O output será semelhante a:
Sending build context to Docker daemon 124.9kB
Step 1/7 : FROM node:12.22.11-buster
12.22.11-buster: Pulling from library/node
b281ebec60d2: Pull complete
74dae484504b: Pull complete
21739e3ef21a: Pull complete
e98d6bb51c7c: Pull complete
517ebafd9747: Pull complete
fa245e9d6fa2: Pull complete
fdeef5999bae: Pull complete
a3b874d3452b: Pull complete
136c54ae3910: Pull complete
Status: Downloaded newer image for node:12.22.11-buster
---> a1e2d899782c
Step 2/7 : WORKDIR /app
---> Running in ee932064af7b
Removing intermediate container ee932064af7b
---> 7e8ca6972b82
Step 3/7 : COPY package*.json ./
---> 9e72e75fab75
Step 4/7 : RUN npm install
---> Running in b0f180a63cc6
added 156 packages from 113 contributors and audited 157 packages in 2.93s
Step 5/7 : COPY . .
---> a4043b8f7fcd
Step 6/7 : EXPOSE 8080
---> Running in 94729dcf37c5
Removing intermediate container 94729dcf37c5
---> d36eb7c82413
Step 7/7 : CMD [ "node" , "server.js" ]
---> Running in dcb21437fb62
Removing intermediate container dcb21437fb62
---> 5b8dd121f597
Successfully built 5b8dd121f597
Successfully tagged pauloazevedo88/conversao-temperatura:v1Usando o comando docker image ls é possível ver a imagem na lista
2-Comando: docker container run -d --rm --name conversor -p 8080:8080 pauloazevedo88/conversao-temperatura:v1 para arrancar com o container
Usando o comando docker container ls é possível listar containers
O output será semelhante a:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
df09053cd2be pauloazevedo/conversao-temperatura:v1 "docker-entrypoint.s…" 10 seconds ago Up 9 seconds 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp conversor3- O container deverá estar disponível acessando: a minha applicação node.js
Passos para criação de cluster, usando k3d, para deployment de pauloazevedo88/conversao-temperatura:v1:1- Comando: docker image push pauloazevedo88/conversao-temperatura:v1 para publicar a imagem no Docker Hub
O output será semelhante a:
The push refers to repository [docker.io/pauloazevedo88/conversao-temperatura]
327c86979d43: Pushed
6c76d3f9a35d: Pushed
9c5b422b48b6: Pushed
5c3a1f687044: Pushed
b396b15272a0: Pushed
5e14cddde987: Pushed
41fb65fa14b3: Pushed
9e6164f16476: Pushed
627d03f17169: Pushed
6b9b07bf46f5: Pushed
88139fe969ab: Pushed
83f556e4c108: Pushed
7362f7f77851: Pushed
v1: digest: sha256:4fe7bec20ee3710563363420ca94675f6337bd9240b00955dc0b0322c6f0620d size: 30512- Instalação do K3d que é uma solução para cluster K8s baseada em Docker.
3- Comando: k3d cluster create clusterconversor --servers 2 --agents 2 -p "8080:30000@loadbalancer"
O output será semelhante a:
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-clusterconversor'
INFO[0000] Created image volume k3d-clusterconversor-images
INFO[0000] Starting new tools node...
INFO[0000] Creating initializing server node
INFO[0000] Creating node 'k3d-clusterconversor-server-0'
INFO[0000] Starting Node 'k3d-clusterconversor-tools'
INFO[0001] Creating node 'k3d-clusterconversor-server-1'
INFO[0001] Creating node 'k3d-clusterconversor-agent-0'
INFO[0001] Creating node 'k3d-clusterconversor-agent-1'
WARN[0001] You're creating 2 server nodes: Please consider creating at least 3 to achieve etcd quorum & fault tolerance
INFO[0001] Creating LoadBalancer 'k3d-clusterconversor-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0002] HostIP: using network gateway 172.22.0.1 address
INFO[0002] Starting cluster 'clusterconversor'
INFO[0002] Starting the initializing server...
INFO[0002] Starting Node 'k3d-clusterconversor-server-0'
INFO[0003] Starting servers...
INFO[0003] Starting Node 'k3d-clusterconversor-server-1'
INFO[0022] Starting agents...
INFO[0022] Starting Node 'k3d-clusterconversor-agent-0'
INFO[0022] Starting Node 'k3d-clusterconversor-agent-1'
INFO[0030] Starting helpers...
INFO[0030] Starting Node 'k3d-clusterconversor-serverlb'
INFO[0037] Injecting records for hostAliases (incl. host.k3d.internal) and for 5 network members into CoreDNS configmap...
INFO[0039] Cluster 'clusterconversor' created successfully!
INFO[0039] You can now use it like this:
kubectl cluster-infoComando: kubectl get nodes
O output será semelhante a:
NAME STATUS ROLES AGE VERSION
k3d-clusterconversor-agent-0 Ready <none> 3m38s v1.22.7+k3s1
k3d-clusterconversor-agent-1 Ready <none> 3m38s v1.22.7+k3s1
k3d-clusterconversor-server-0 Ready control-plane,etcd,master 3m54s v1.22.7+k3s1
k3d-clusterconversor-server-1 Ready control-plane,etcd,master 3m42s v1.22.7+k3s15- Comando: kubectl apply -f Deployment.yaml
O output será semelhante a:
deployment.apps/meudeployment created
service/web createdComando: kubectl get all
O output será semelhante a:
NAME READY STATUS RESTARTS AGE
pod/meudeployment-cd98fdbf9-2h2ht 1/1 Running 0 2m19s
pod/meudeployment-cd98fdbf9-hs6sr 1/1 Running 0 2m19s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 8m25s
service/web NodePort 10.43.125.108 <none> 80:30000/TCP 2m19s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/meudeployment 2/2 2 2 2m19s
NAME DESIRED CURRENT READY AGE
replicaset.apps/meudeployment-cd98fdbf9 2 2 2 2m19s6- O container deverá estar disponível acessando: a minha applicação node.js
Usando o cluster já criado na DigitalOcean para deployment de Conversao Temperatura usando CICD Github Actions:Para consultar novos deployments: Comando: kubectl get all O output será semelhante a:
NAME READY STATUS RESTARTS AGE
pod/meudeployment-5f66976b8d-qn5tl 1/1 Running 0 48s
pod/meudeployment-5f66976b8d-xjpzj 1/1 Running 0 54s
pod/mongo-6d595f4df-gnzqd 1/1 Running 0 158m
pod/mongodb-66b8d4645-pq974 1/1 Running 0 5h35m
pod/rottentomatoes-64d7d98554-m8tjc 1/1 Running 0 149m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.245.0.1 <none> 443/TCP 6h15m
service/mongo ClusterIP 10.245.89.238 <none> 27017/TCP 158m
service/mongodb ClusterIP 10.245.76.253 <none> 27017/TCP 5h35m
service/rottentomatoes LoadBalancer 10.245.171.186 174.138.104.251 80:30000/TCP 5h35m
service/web LoadBalancer 10.245.100.2 167.99.17.192 80:31555/TCP 13m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/meudeployment 2/2 2 2 13m
deployment.apps/mongo 1/1 1 1 158m
deployment.apps/mongodb 1/1 1 1 5h35m
deployment.apps/rottentomatoes 1/1 1 1 5h35m
NAME DESIRED CURRENT READY AGE
replicaset.apps/meudeployment-5f66976b8d 2 2 2 55s
replicaset.apps/meudeployment-bd6464cd5 0 0 0 13m
replicaset.apps/mongo-6d595f4df 1 1 1 158m
replicaset.apps/mongodb-66b8d4645 1 1 1 5h35m
replicaset.apps/rottentomatoes-5ddf58f599 0 0 0 158m
replicaset.apps/rottentomatoes-64d7d98554 1 1 1 149m
replicaset.apps/rottentomatoes-6bdcf4996 0 0 0 164m
replicaset.apps/rottentomatoes-cf7f4b4fd 0 0 0 5h35mApplicação disponível acessando: a minha applicação node.js