Skip to content

README-04.md

Latest commit

 

History

History
846 lines (678 loc) · 30.5 KB

README-04.md

File metadata and controls

846 lines (678 loc) · 30.5 KB

Details

Click to Contract/Expend

Section 4 - Orchestrating Collections of Services with Kubernetes

63. Installing Kubernetes

Click Docker Icon on the tray -> Preferences -> Kubernetes -> Enable Kubernetes

Currently Kubernetes v1.21.3

64. IMPORTANT Note for Minikube and MicroK8s Users

  1. Minikube Users

Recent versions of Minikube will use the docker driver by default when you run minikube start. On Windows or macOS, the docker driver is not compatible with an ingress, which we will be using throughout the course.

To avoid this issue, you can pass the --driver flag with a specific driver or --vm=true

# macOS:
minikube start --vm=true
minikube start --driver=hyperkit
minikube start --driver=virtualbox

# Windows:
minikube start --vm=true
minikube start --driver=hyperv
minikube start --driver=virtualbox
  1. MicroK8s Users

This course does not support the use of MicroK8s and will likely not work in the way that is presented. We highly suggest the use of Docker Desktop for macOS and Windows users and Minikube for Linux users. If you choose to use MicroK8s you will need to do your own research and refactoring to resolve the issues that may arise.

65. A Kubernetes Tour

kubectl version
# Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"darwin/amd64"}
# Unable to connect to the server: dial tcp: lookup 68FE2F410B3C62C1D26A3CF89A9FDEA0.gr7.ap-southeast-2.eks.amazonaws.com on 8.8.8.8:53: no such host

At first it shows Unable to connect to the server.
It will be solved after minikube start --vm=true as it will install the server and change the config

kubectl config view

kubectl

minikube start --vm=true
# 😄  minikube v1.21.0 on Darwin 11.6
# 🎉  minikube 1.24.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.24.0
# 💡  To disable this notice, run: 'minikube config set WantUpdateNotification false'

# ✨  Automatically selected the hyperkit driver
# 💾  Downloading driver docker-machine-driver-hyperkit:
#     > docker-machine-driver-hyper...: 65 B / 65 B [----------] 100.00% ? p/s 0s
#     > docker-machine-driver-hyper...: 10.52 MiB / 10.52 MiB  100.00% 4.60 MiB p
# 🔑  The 'hyperkit' driver requires elevated permissions. The following commands will be executed:

#     $ sudo chown root:wheel /Users/noah/.minikube/bin/docker-machine-driver-hyperkit
#     $ sudo chmod u+s /Users/noah/.minikube/bin/docker-machine-driver-hyperkit


# Password:
# 💿  Downloading VM boot image ...
#     > minikube-v1.21.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
#     > minikube-v1.21.0.iso: 243.03 MiB / 243.03 MiB [] 100.00% 5.51 MiB p/s 44s
# 👍  Starting control plane node minikube in cluster minikube
# 🔥  Creating hyperkit VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
# 🐳  Preparing Kubernetes v1.20.7 on Docker 20.10.6 ...
#     ▪ Generating certificates and keys ...
#     ▪ Booting up control plane ...
#     ▪ Configuring RBAC rules ...
# 🔎  Verifying Kubernetes components...
#     ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
# 🌟  Enabled addons: default-storageclass, storage-provisioner
# 🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
  • Mater
    • Service
      • Node
        • Pod (= Container)
        • Pod and Container are technically different, but we will use one to one mapping

66. Important Kubernetes Terminology

  • Kubernetes Cluster : A collections of nodes + a master to manage them
  • Node: A Virtual machine that will run our containers
  • Pod: More or less a running container. Technically, a pod can run multiple containers (we won't do this)
  • Deployment: Monitors a set of pods, make sure they are running and restarts them if they crash
  • Service: Provides an easy-to-remember URL to access a running container

67. Notes on Config Files

Do not create Objects without config files. Config files provide a precise definition of what your cluster is running.
Kubernetes docs will tell you to run direct commands to create objects - only do this for testing purposes

68. Creating a Pod

# blog/posts
docker build -t pcsmomo/posts:0.0.1 .
# blog/infra/k8s
kubectl apply -f posts.yaml
# pod/posts created
kubectl get pods
# | NAME  | READY |      STATUS      | RESTARTS | AGE |
# | :---: | :---: | :--------------: | :------: | :-: |
# | posts |  0/1  | ImagePullBackOff |    0     | 35s |

69. ErrImagePull, ErrImageNeverPull and ImagePullBackoff Errors

# blog/infra/k8s
kubectl delete -f posts.yaml
# pod "posts" deleted

add imagePullPolicy: Never to posts.yaml

kubectl apply -f .
# pod/posts created
kubectl get pods
# NAME    READY   STATUS    RESTARTS   AGE
# posts   1/1     Running   0          3s

Probably...

I guess before delete and create, I did this too

eval $(minikube docker-env)
# Note - this comment will need to be repeated anytime you close and restart the terminal session
docker build -t USERNAME/REPO .
kubectl apply -f infra/k8s/

But turns out, I don't need to run that eval command, after testing

# K8s is extensible - we can add in our own custom objects. This specifies the set of objects we want K8s to look at
apiVersion: v1

# The type of object we want to create
kind: Pod

# Config options for the object we are about to create
metadata:
  # When the pod is created, give it a name of 'posts'
  name: posts
# The exact attributes we want to apply to the object we are about to create
spec:
  # We can create many containers in a single pod
  containers:
    # Make a container with a name of 'posts'
    - name: posts
      # The exact image we want to use
      image: pcsmomo/posts:0.0.1
      imagePullPolicy: Never

image: pcsmomo/posts or image: pcsmomo/posts:latest
if we don't specify the tag, it will try to reach docker hub to find the image:latest
and in our case, we will get an error as we didn't push our image to docker hub

71. Common Kubectl Commands

Docker World K8s World
docker ps kubectl get pods
docker exec -it [container_id] [cmd] kubectl exec -it [pod_name] [cmd]
docker logs [container_id] kubectl logs [pod_name]
kubectl delete pod [pod_name]
kubectl apply -f [config_file_name]
kubectl describe pod [pod_name] 
kubectl exec -it posts sh
ls
# if we run more than two containers in a pod, we need to specify which container we want to execute
kubectl logs posts

73. Introducing Deployments

When we run 3 posts pods,

  1. if one Pod is down, deployment manages to keep 3 pods runnning.
  2. when new version is deployed, deployment running 3 new version pods first and then kill 3 old version pods

74. Creating a Deployment

kubectl apply -f posts-depl.yaml
kubectl get deployments
kubectl describe deployment [depl_name]
kubectl apply -f [config_file_name]
kubectl delete deployment [depl_name]

75. Common Commands Around Deployments

kubectl get deployments
# NAME         READY   UP-TO-DATE   AVAILABLE   AGE
# posts-depl   1/1     1            1           7s
kubectl get pods
# NAME                          READY   STATUS    RESTARTS   AGE
# posts-depl-7b58d6bb87-kx65s   1/1     Running   0          53s
kubectl delete pod posts-depl-7b58d6bb87-kx65s
# the pod will be delete but deployment creates a new pod immediately
kubectl describe deployment posts-depl

76. Updating Deployments

Updating the image used by a deployment

  1. Method #1 - using local
    1. 'blog/posts': update index.js code
    2. 'blog/posts': rebuild: docker build -t pcsmomo/posts:0.0.2 .
    3. 'blog/infra/k8s': update posts-depl.yaml file
    4. 'blog/infra/k8s':apply kubectl apply -f posts-depl.yaml

Howover, this method is not really useful because we need to manually change the tag version on the yaml file

77. Preferred Method for Updating Deployments

  1. *Method #2 - using docker hub
    1. 'blog/infra/k8s': using 'latest' or remove tag in the pod spec section
    2. 'blog/posts': update index.js code
    3. 'blog/posts': rebuild: docker build -t pcsmomo/posts:0.0.2 .
    4. push to the docker hub docker push pcsmomo/posts
    5. 'blog/infra/k8s': run the commend
      • kubectl rollout restart deployment [depl_name]
kubectl get deployments
kubectl rollout restart deployment posts-depl
kubectl get deployments
kubectl get pods
# NAME                          READY   STATUS        RESTARTS   AGE
# posts-depl-6989986b47-7rrf9   1/1     Running       0          17s
# posts-depl-76c9d74774-sp788   0/1     Terminating   0          6m47s
kubectl logs posts-depl-6989986b47-7rrf9

78. Networking With Services

  • *Cluster IP
    • Set up easy-to-remember URL to access a pod.
    • Only exposes pods in the cluster
  • Node Port
    • Makes a pod accessible from outside the cluster.
    • Usually only used for dev purposes.
  • *Load Balancer
    • Makes a pod accessible from outside the cluster.
    • This is the right way to expose a pod to the outside world
  • External Name
    • Redirects an in-cluster request to a CNAME url...
    • don't worry about this one

79. Creating a NodePort Service

apiVersion: v1
kind: Service
metadata:
  name: posts-srv
spec:
  type: NodePort
  selector:
    app: posts # matching with deployment template labels
  ports:
    - name: posts # optional
      protocol: TCP
      port: 4000 # outer: port for service itself
      targetPort: 4000 # inter: to the pod

80. Accessing NodePort Services

# blog/infra/k8s
kubectl apply -f posts-srv.yaml
# service/posts-srv created
kubectl get services
# NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
# kubernetes   ClusterIP   10.96.0.1       <none>        443/TCP          23h
# posts-srv    NodePort    10.105.88.106   <none>        4000:30551/TCP   51s
kubectl describe service posts-srv
minikube ip
# 192.168.64.2
  • PORT(S): 4000:30551/TCP\
    • 30551: nodePort randomly assigned

We can connect

  • Docker for Mac/Windows - localhost:3xxxx/posts
  • Docker Toolbox with Minikube - 192.168.64.2:30551/posts

81. Setting Up Cluster IP Services

  • Posts Pod -> Cluster IP service for Event Bus -> Event Bus Pod
  • Event Bus Pod -> Cluster IP service for Posts -> Posts Pod

82. Building a Deployment for the Event Bus

  1. Build an image for the Event Bus
  2. Push the image to Docker hub
  3. Create a deployment for Event Bus
  4. Create a Cluster IP service for Event Bus and Posts
  5. Wire it all up! -> 'localhost' to <service_name>
# blog/event-bus
docker build -t pcsmomo/event-bus .
docker push pcsmomo/event-bus
touch event-bus-depl.yaml
# blog/infra/k8s
kubectl apply -f event-bus-depl.yaml
# deployment.apps/event-bus-depl created
kubectl get pods
# NAME                              READY   STATUS    RESTARTS   AGE
# event-bus-depl-668857b468-qk5vd   1/1     Running   0          24s
# posts-depl-6989986b47-7rrf9       1/1     Running   1          9h

83. Adding ClusterIP Services

kubectl apply -f event-bus-depl.yaml
# deployment.apps/event-bus-depl unchanged
# service/event-bus-srv created
kubectl apply -f posts-depl.yaml
# deployment.apps/posts-depl unchanged
# service/posts-clusterip-srv created
kubectl get pods
# NAME                  TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
# event-bus-srv         ClusterIP   10.99.99.77     <none>        4005/TCP         3m23s
# kubernetes            ClusterIP   10.96.0.1       <none>        443/TCP          23h
# posts-clusterip-srv   ClusterIP   10.96.25.216    <none>        4000/TCP         9s
# posts-srv             NodePort    10.105.88.106   <none>        4000:30551/TCP   37m

85. Updating Service Addresses

# blog/event-bus
docker build -t pcsmomo/event-bus .
docker push pcsmomo/event-bus
# blog/posts
docker build -t pcsmomo/posts .
docker push pcsmomo/posts
# blog/infra/k8s
kubectl get deployments
# NAME             READY   UP-TO-DATE   AVAILABLE   AGE
# event-bus-depl   1/1     1            1           26m
# posts-depl       1/1     1            1           9h
kubectl rollout restart deployment posts-depl
# deployment.apps/posts-depl restarted
kubectl rollout restart deployment event-bus-depl
# deployment.apps/event-bus-depl restarted
kubectl get pods
# NAME                             READY   STATUS    RESTARTS   AGE
# event-bus-depl-f7bf7b948-x5nkz   1/1     Running   0          24s
# posts-depl-94d556dcd-xk5t6       1/1     Running   0          47s

86. Verifying Communication

kubectl exec -it posts-depl-94d556dcd-bqrdf sh
cat index.js
# the address is not changed

# rebuild and push and rollout restart
docker build -t pcsmomo/posts .
docker push pcsmomo/posts
kubectl rollout restart deployment posts-depl
# somehow rollout does not work

kubectl delete deployment post-depl
kubectl apply -f posts-depl.yaml

87. Adding Query, Moderation and Comments

# blog/comments
docker build -t pcsmomo/comments .
docker push pcsmomo/comments
# blog/moderation
docker build -t pcsmomo/moderation .
docker push pcsmomo/moderation
# blog/query
docker build -t pcsmomo/query .
docker push pcsmomo/query
# blog/infra/k8s
kubectl apply -f .
kubectl get pods
kubectl get services

88. Testing Communication

# blog/event-bus
docker build -t pcsmomo/event-bus .
docker push pcsmomo/event-bus
# blog/infra/k8s
kubectl rollout restart deployment event-bus-depl
kubectl get pods
# NAME                               READY   STATUS    RESTARTS   AGE
# comments-depl-76b7f795-gkjdc       1/1     Running   0          5m47s
# event-bus-depl-779b56dfd9-p6l8z    1/1     Running   0          2m10s
# moderation-depl-66dddc44d5-9xnzc   1/1     Running   0          5m46s
# posts-depl-5494775c9b-7z2h9        1/1     Running   1          13h
# query-depl-59b5f86c4f-m6d9n        1/1     Running   0          5m46s

And postman test!

89. Load Balancer Services

React App need to communicate with all services (except moderation)

  1. Option #1 - Probably not good
    • React App -> Node Port for each service
  2. *Option #2 - Probably good
    • React App -> Load Balancer Service -> Cluster IP for each service

90. Load Balancers and Ingress

  • Load Balancer Service
    • Tell Kubernetes to reach out to its provider and provision a load balancer
    • Gets traffic in to a single pod
    • Load Balancer is actually in a cloud provider
  • Ingress or Ingress Controller
    • A pod with a set of routing rules to distribute traffic to other services

React App -> Load Balancer -> Ingress Controller -> Pod

91. Update on Ingress Nginx Mandatory Commands

In the upcoming lecture, we will be installing Ingress Nginx. In the video, it is shown that there is a required mandatory command that needed to be run for all providers. This has since been removed, so, the provider-specific commands (Docker Desktop, Minikube, etc) are all that is required.

https://kubernetes.github.io/ingress-nginx/deploy/#environment-specific-instructions

92. Installing Ingress-Nginx

ingress-nginx

Note, not 'kubernetes-ingress'

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.0/deploy/static/provider/cloud/deploy.yaml

# Environment-specific instructions¶
minikube addons enable ingress
    # ▪ Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
    # ▪ Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
    # ▪ Using image k8s.gcr.io/ingress-nginx/controller:v0.44.0
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                         │
│    😿  If the above advice does not help, please let us know:                                                           │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                                                         │
│                                                                                                                         │
│    Please attach the following file to the GitHub issue:                                                                │
│    - /var/folders/gj/j9_ldgqd3rn0pghfmfllqp600000gn/T/minikube_addons_372143d00872dcadc2a2a64cd091e7aa9a32d396_3.log    │
│                                                                                                                         │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
# eventually it fails

93. Ingress v1 API Required Update

94. Writing Ingress Config Files

Ingress Controller

# blog/infra/k8s
kubectl apply -f ingress-srv.yaml
# Error from server (InternalError): error when creating "ingress-srv.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": an error on the server ("") has prevented the request from succeeding

Stackoverflow solution

kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission
# validatingwebhookconfiguration.admissionregistration.k8s.io "ingress-nginx-admission" deleted
kubectl apply -f ingress-srv.yaml
# ingress.networking.k8s.io/ingress-srv created

95. Important Note About Port 80

sudo lsof -i tcp:80
kubectl get services -n ingress-nginx
kubectl get pods -n ingress-nginx

96. Hosts File Tweak

code /etc/hosts
# Studying udemy microservices - minikube ip
192.168.64.2 posts.com

Navigate posts.com/posts -> I cannot connect

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.0/deploy/static/provider/cloud/deploy.yaml
kubectl delete -f .
kubectl apply -f .
kubectl delete -A ValidatingWebhookConfiguration ingress-nginx-admission
kubectl apply -f ingress-srv.yaml
kubectl get service ingress-nginx-controller --namespace=ingress-nginx

I cannot go furtuer.. Stop until I find a solution..

Steps

  1. docker running
  2. kubernetes running
  3. minikube start --vm=true
    • minikube ip : 192.168.64.2
    • kubectl get pods : posts-srv NodePort : port number : 30551

Then I can connect 192.168.64.2:30551/posts, but ingress

  1. minikube addons enable ingress
    • failed to install
  2. eval $(minikube docker-env)
  3. change /etc/hosts

I can access posts.com:30551/posts, but
I cannot connect posts.com/posts
it seems like ingress load balance does not work on my environment

kubectl get services -n ingress-nginx
# NAME                                 TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
# ingress-nginx-controller             LoadBalancer   10.109.99.78   <pending>     80:32109/TCP,443:31073/TCP   6m48s
# ingress-nginx-controller-admission   ClusterIP      10.98.249.55   <none>        443/TCP                      6m48s
kubectl get pods -n ingress-nginx
# NAME                                        READY   STATUS      RESTARTS   AGE
# ingress-nginx-admission-create-nkz2c        0/1     Completed   0          28s
# ingress-nginx-admission-patch-hsjb9         0/1     Completed   1          27s
# ingress-nginx-controller-69db7f75b4-wmmgs   1/1     Running     0          28s
# another attempt
# https://github.com/kubernetes/minikube/issues/11108
minikube config set vm-driver hyperkit
# ❗  These changes will take effect upon a minikube delete and then a minikube start
minikube delete
# 🔥  Deleting "minikube" in hyperkit ...
# 💀  Removed all traces of the "minikube" cluster.
minikube start
# 😄  minikube v1.21.0 on Darwin 11.6
# ✨  Using the hyperkit driver based on user configuration
# 👍  Starting control plane node minikube in cluster minikube
# 🔥  Creating hyperkit VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
# 🔥  Deleting "minikube" in hyperkit ...
# 🤦  StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for a6:1c:10:a6:10:6e
# 🔥  Creating hyperkit VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
# 🐳  Preparing Kubernetes v1.20.7 on Docker 20.10.6 ...
#     ▪ Generating certificates and keys ...
#     ▪ Booting up control plane ...
#     ▪ Configuring RBAC rules ...
# 🔎  Verifying Kubernetes components...
#     ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
# 🌟  Enabled addons: default-storageclass, storage-provisioner
# 🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
minikube addons enable ingress
#     ▪ Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
#     ▪ Using image docker.io/jettech/kube-webhook-certgen:v1.5.1
#     ▪ Using image k8s.gcr.io/ingress-nginx/controller:v0.44.0
# 🔎  Verifying ingress addon...
# 🌟  The 'ingress' addon is enabled

# blog/infra/k8s
kubectl apply -f .
# deployment.apps/comments-depl created
# service/comments-srv created
# deployment.apps/event-bus-depl created
# service/event-bus-srv created
# ingress.networking.k8s.io/ingress-srv created
# deployment.apps/moderation-depl created
# service/moderation-srv created
# deployment.apps/posts-depl created
# service/posts-clusterip-srv created
# service/posts-srv created
# deployment.apps/query-depl created
# service/query-srv created
kubectl get pods
# comments-depl-76b7f795-swnsv       1/1     Running   0          2m35s
# event-bus-depl-668857b468-mzb56    1/1     Running   0          2m34s
# moderation-depl-66dddc44d5-vr46x   1/1     Running   0          2m34s
# posts-depl-5494775c9b-6wcwt        1/1     Running   0          2m33s
# query-depl-59b5f86c4f-5rfpx        1/1     Running   0          2m33s
kubectl get services -n ingress-nginx
# NAME                                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
# ingress-nginx-controller             NodePort    10.107.169.175   <none>        80:32292/TCP,443:32369/TCP   4m31s
# ingress-nginx-controller-admission   ClusterIP   10.104.147.242   <none>        443/TCP                      4m31s
kubectl get pods -n ingress-nginx
# NAME                                        READY   STATUS      RESTARTS   AGE
# ingress-nginx-admission-create-prpgg        0/1     Completed   0          4m24s
# ingress-nginx-admission-patch-lt6zk         0/1     Completed   2          4m24s
# ingress-nginx-controller-5d88495688-v5ltk   1/1     Running     0          4m24s
minikube ip 192.168.64.3

Damn T_T, it succeeded

97. Important Note to Add Environment Variable

[React-Scripts] v3.4.1 fails to start in Docker #8688

# blog/client/Dockerfile
FROM node:alpine

# Add the following line
ENV CI=true

WORKDIR /app

98. Deploying the React App

# blog/client
docker build -t pcsmomo/client .
docker push pcsmomo/client
# blog/infra/k8s
kubectl apply -f client-depl.yaml
# deployment.apps/client-depl created
# service/client-srv created

99. Unique Route Paths

Now client can access backend via Ingress
But the problem is that Ingress doesn't distinguish methods such as POST and GET

  • posts: POST /posts
  • query: GET /posts

We need to modify them to unique routh paths

  • posts: POST /posts -> /posts/create
  • query: GET /posts
# blog/client
docker build -t pcsmomo/client .
docker push pcsmomo/client
# blog/posts
docker build -t pcsmomo/posts .
docker push pcsmomo/posts
# blog/infra/k8s
kubectl rollout restart client-depl.yaml
kubectl rollout restart posts-depl.yaml

100. Final Route Config

  • for /posts/:id/comments, nginx doesn't support wild card thing
    • so we need to use regular expression, /posts/?(.*)/comments
  • client has to have all rest paths, so it needs to be defined at the last 
    - path: /?(.*)
  pathType: Prefix
  backend:
    service:
      name: client-srv
      port:
        number: 3000
# blog/infra/k8s
kubectl apply -f ingress-srv.yaml
# ingress.networking.k8s.io/ingress-srv configured

Navigate http://posts.com/ and create post.
When refresh the page, 502 error from query service.
app has crashed before when it connects to http://event-bus-srv:4005/events\

kubectl logs query-depl-59b5f86c4f-5rfpx
kubectl delete pod query-depl-59b5f86c4f-5rfpx
kubectl get pods
# new query-depl pod is running

Navigate http://posts.com/ and create a new post / refresh / create a new comment / refresh

All Good!

101. Introducing Skaffold

Skaffold - when code changes, it applies to the pod (...nodemon?)

  • Automates many tasks in a Kubernetes dev environment
  • Makes it really easy to update code in a running pod
  • Makes it really easy to create/delete all objects tied to a proejct at once
  • skaffold.dev
  • Skaffold Documentation
brew install skaffold

102. Skaffold Setup

build:
  local:
    # default is true, pushing docker image
    push: false

103. First Time Skaffold Startup

skaffold dev
# unable to stream build output: Get https://registry-1.docker.io/v2/library/node/manifests/sha256:8569c8f07454ec42501e5e40a680e49d3f9aabab91a6c149e309bac63a3c8d54: dial tcp: lookup registry-1.docker.io on 192.168.64.1:53: read udp 192.168.64.3:39871->192.168.64.1:53: i/o timeout. Please fix the Dockerfile and try again..
skaffold dev
# It hung..

Again...........................................

It's very slow and not working well for me.
(I may need a new laptop)

2nd Attempt

  • Reboot my laptop
  • Run docker (including Kubernetes)
minikube stop
# ✋  Stopping node "minikube"  ...
# 🛑  1 nodes stopped.
skaffold dev
# It builds all the images again and creating it's own dev server
# Listing files to watch...
# ...
# It takes more than 10 mins in my laptop

all docker images are built, but errored when deploying

# Tags used in deployment:
#  - pcsmomo/client -> pcsmomo/client:98390a7ecb0f9625cff02f6773c3c0d95bbae41268e5e69504727535dc94b67c
#  - pcsmomo/comments -> pcsmomo/comments:bc8f694d9d2532df158e8b732ccfbc859681e0bef44329d9c482c8dd846d7c95
#  - pcsmomo/event-bus -> pcsmomo/event-bus:768d4565a9a6ad3f0b8b855691c0807dc92b9cbd44a9bbacc3d3e008c5c799da
#  - pcsmomo/moderation -> pcsmomo/moderation:f519c4c6837b4bbf45bffb0f4a688b3218a7c930dbdad5865778131a512dc4d2
#  - pcsmomo/posts -> pcsmomo/posts:c3bfe073cc3c6877d80ef4cf33df5e61b7fe05adb7afbd5f787d16d7ba366184
#  - pcsmomo/query -> pcsmomo/query:ec3011b7f94fdcb97502512474a00d9b6cc1b577dc50cc82897126b988e31782
# Starting deploy...
# Cleaning up...
# WARN[0563] deployer cleanup:kubectl create: running [kubectl --context  create --dry-run=client -oyaml -f /Users/noah/Documents/Study/Study_codes/udemy/microservices-node-react/microservices-node-react-git/04-with-kubernetes/blog/infra/k8s/client-depl.yaml
# ...
#  - stdout: ""
#  - stderr: "The connection to the server localhost:8080 was refused - did you specify the right host or port?\n"
#  - cause: exit status 1  subtask=-1 task=DevLoop
# unable to connect to Kubernetes: getting client config for Kubernetes client: error creating REST client config in-cluster: unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined
# https://skaffold.dev/docs/quickstart/
minikube start --profile custom
# 😿  Failed to start hyperkit VM. Running "minikube delete -p custom" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for aa:2c:f6:cc:5:b1

# ❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP address never found in dhcp leases file Temporary error: could not find an IP address for aa:2c:f6:cc:5:b1

# ╭────────────────────────────────────────────────────────────────────╮
# │                                                                    │
# │    😿  If the above advice does not help, please let us know:      │
# │    👉  https://github.com/kubernetes/minikube/issues/new/choose    │
# │                                                                    │
# │    Please attach the following file to the GitHub issue:           │
# │    - /Users/noah/.minikube/logs/lastStart.txt                      │
# │                                                                    │
# ╰────────────────────────────────────────────────────────────────────╯
skaffold config set --global local-cluster true
eval $(minikube -p custom docker-env)
minikube config set vm-driver hyperkit
minikube delete
minikube start --profile custom
# minikube addons enable ingress
skaffold config set --global local-cluster true
eval $(minikube -p custom docker-env)
skaffold dev
# Starting deploy...
# Cleaning up...
# Deploy Failed. Could not connect to cluster due to "https://192.168.64.4:8443/version?timeout=32s": dial tcp 192.168.64.4:8443: i/o timeout. Check your connection for the cluster.
minikube ip -p custom
minikube status -p custom