-
Notifications
You must be signed in to change notification settings - Fork 0
/
Docker_dia3_K8S
427 lines (379 loc) · 13.9 KB
/
Docker_dia3_K8S
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
Vamos falar de deployment
YAML para o deploy de 3 replicas do nginx
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: nginx-deployment
name: nginx-deployment
spec:
replicas: 3
selector:
matchLabels:
app: nginx-deployment
strategy: {}
template:
metadata:
labels:
app: nginx-deployment
spec:
containers:
- image: nginx
name: nginx
resources:
limits:
cpu: "500m"
memory: 256Mi
requests:
cpu: "300m"
memory: 128Mi
kubectl get deployments.apps
NAME READY UP-TO-DATE AVAILABLE AGE
nginx-deployment 3/3 3 3 113s
root@obi-System-Product-Name:~/k8s/day3#
kubectl get deployments.apps -o yaml
apiVersion: v1
items:
- apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "1"
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"labels":{"app":"nginx-deployment"},"name":"nginx-deployment","namespace":"default"},"spec":{"replicas":3,"selector":{"matchLabels":{"app":"nginx-deployment"}},"strategy":{},"template":{"metadata":{"labels":{"app":"nginx-deployment"}},"spec":{"containers":[{"image":"nginx","name":"nginx","resources":{"limits":{"cpu":"500m","memory":"256Mi"},"requests":{"cpu":"300m","memory":"128Mi"}}}]}}}}
creationTimestamp: "2024-05-23T01:19:03Z"
generation: 1
labels:
app: nginx-deployment
name: nginx-deployment
namespace: default
resourceVersion: "10627"
uid: 281b8650-fc75-4c80-99ea-a8c96f59fb06
spec:
progressDeadlineSeconds: 600
replicas: 3
revisionHistoryLimit: 10
selector:
matchLabels:
app: nginx-deployment
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
app: nginx-deployment
spec:
containers:
- image: nginx
imagePullPolicy: Always
name: nginx
resources:
limits:
cpu: 500m
memory: 256Mi
requests:
cpu: 300m
memory: 128Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
terminationGracePeriodSeconds: 30
status:
availableReplicas: 3
conditions:
- lastTransitionTime: "2024-05-23T01:19:12Z"
lastUpdateTime: "2024-05-23T01:19:12Z"
message: Deployment has minimum availability.
reason: MinimumReplicasAvailable
status: "True"
type: Available
- lastTransitionTime: "2024-05-23T01:19:03Z"
lastUpdateTime: "2024-05-23T01:19:12Z"
message: ReplicaSet "nginx-deployment-9bb44bfdb" has successfully progressed.
reason: NewReplicaSetAvailable
status: "True"
type: Progressing
observedGeneration: 1
readyReplicas: 3
replicas: 3
updatedReplicas: 3
kind: List
metadata:
resourceVersion: ""
Trazer somente os pods que utilizando a label criada no deployment (app=nginx-deployment)
kubectl get pods -l app=nginx-deployment
NAME READY STATUS RESTARTS AGE
nginx-deployment-9bb44bfdb-9nkg5 1/1 Running 0 5m25s
nginx-deployment-9bb44bfdb-tr7bb 1/1 Running 0 5m25s
nginx-deployment-9bb44bfdb-w8rs2 1/1 Running 0 5m25s
kubectl get replicasets (esse é o cara que é consultado para saber se esta ok com as replicas, replicasets)
NAME DESIRED CURRENT READY AGE
nginx-deployment-9bb44bfdb 3 3 3 7m2s
==================================================
kubectl get deployment -o yaml
Criar um deploymente via linha de comando
kubectl create deployment --image nginx --replicas 2 nginx-deployment01
root@obi-System-Product-Name:~/k8s/day3# kubectl get deployment
NAME READY UP-TO-DATE AVAILABLE AGE
nginx-deployment01 2/2 2 2 8s
root@obi-System-Product-Name:~/k8s/day3# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-deployment01-77774f6685-2dtmq 1/1 Running 0 16s
nginx-deployment01-77774f6685-khjb5 1/1 Running 0 16s
obivas01 1/1 Running 2 (15h ago) 4d23h (antigo)
root@obi-System-Product-Name:~/k8s/day3#
Comando para gerar o yaml do deployment
kubectl create deployment --image nginx --replicas 2 nginx-deployment01 --dry-run=client -o yaml
root@obi-System-Product-Name:~/k8s/day3# kubectl get po
NAME READY STATUS RESTARTS AGE
nginx-deployment01-77774f6685-dvtp9 1/1 Running 0 11s
nginx-deployment01-77774f6685-vwfmp 1/1 Running 0 11s
Acessar o pod do deployment
kubectl exec -ti nginx-deployment01-77774f6685-dvtp9 -- bash
Vamos criar um deploy com 10 replicas, com namespace e trocar a versão do nginx
Primeiramento criamos a namespace
kubectl create namespace obivas
kubectl get namespace
NAME STATUS AGE
default Active 5d
kube-node-lease Active 5d
kube-public Active 5d
kube-system Active 5d
local-path-storage Active 5d
obivas Active 5m4s
Ou tb podemos fazer via yaml
kubectl create namespace obivas --dry-run=client -o yaml > namespaceobivas.yaml
Esse foi o arquivo gerado
apiVersion: v1
kind: Namespace
metadata:
creationTimestamp: null
name: obivas
spec: {}
status: {}
Agora criar o namespace utilizando o yaml
kubectl apply -f namespaceobivas.yaml
namespace/obivas created
root@obi-System-Product-Name:~/k8s/day3# kubectl get namespace
NAME STATUS AGE
default Active 5d
kube-node-lease Active 5d
kube-public Active 5d
kube-system Active 5d
local-path-storage Active 5d
obivas Active 9s
root@obi-System-Product-Name:~/k8s/day3#
Após criar o namespace vamos subir o deploymento.
root@obi-System-Product-Name:~/k8s/day3# kubectl apply -f deployment.yaml
deployment.apps/nginx-deployment created
Mas para consultar o novo deploymente o comando
kubectl get deployment, não irá funcionar, pois criamos em outra namespace e não mais a default
root@obi-System-Product-Name:~/k8s/day3# kubectl get deployment
No resources found in default namespace.
Temos que o usar o comando com o -n aonde quer dizer namespace e o nome dela
root@obi-System-Product-Name:~/k8s/day3# kubectl get deployment -n obivas
NAME READY UP-TO-DATE AVAILABLE AGE
nginx-deployment 10/10 10 10 17s
root@obi-System-Product-Name:~/k8s/day3#
kubectl describe deployments.apps -n obivas nginx-deployment
Name: nginx-deployment
Namespace: obivas
CreationTimestamp: Mon, 27 May 2024 21:04:57 -0300
Labels: app=nginx-deployment
Annotations: deployment.kubernetes.io/revision: 2
Selector: app=nginx-deployment
Replicas: 10 desired | 10 updated | 10 total | 10 available | 0 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 25% max unavailable, 25% max surge
Pod Template:
Labels: app=nginx-deployment
Containers:
nginx:
Image: nginx:1.16.0
Port: <none>
Host Port: <none>
Limits:
cpu: 500m
memory: 256Mi
Requests:
cpu: 300m
memory: 128Mi
Environment: <none>
Mounts: <none>
Volumes: <none>
Node-Selectors: <none>
Tolerations: <none>
Conditions:
Type Status Reason
---- ------ ------
Available True MinimumReplicasAvailable
Progressing True NewReplicaSetAvailable
OldReplicaSets: nginx-deployment-7b94797f99 (0/0 replicas created)
NewReplicaSet: nginx-deployment-55f57548b6 (10/10 replicas created)
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ScalingReplicaSet 5m54s deployment-controller Scaled up replica set nginx-deployment-7b94797f99 to 10
Normal ScalingReplicaSet 2m17s deployment-controller Scaled up replica set nginx-deployment-55f57548b6 to 3
Normal ScalingReplicaSet 2m17s deployment-controller Scaled down replica set nginx-deployment-7b94797f99 to 8
Normal ScalingReplicaSet 2m16s deployment-controller Scaled up replica set nginx-deployment-55f57548b6 to 5
Normal ScalingReplicaSet 2m9s deployment-controller Scaled down replica set nginx-deployment-7b94797f99 to 7
Normal ScalingReplicaSet 2m9s deployment-controller Scaled up replica set nginx-deployment-55f57548b6 to 6
Normal ScalingReplicaSet 2m8s deployment-controller Scaled down replica set nginx-deployment-7b94797f99 to 6
Normal ScalingReplicaSet 2m8s deployment-controller Scaled up replica set nginx-deployment-55f57548b6 to 7
Normal ScalingReplicaSet 2m7s deployment-controller Scaled down replica set nginx-deployment-7b94797f99 to 5
Normal ScalingReplicaSet 2m5s (x6 over 2m7s) deployment-controller (combined from similar events): Scaled down replica set nginx-deployment-7b94797f99 to 0
COmando para pegar a versão do nginx rodando no pod
kubectl exec -ti -n obivas nginx-deployment-55f57548b6-6ckdr -- nginx -v
nginx version: nginx/1.16.0
============================================
Agora vamos ver sobre estrategias de deploymente
Usaremos a default iniciamento para o entendimento
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: nginx-deployment
name: nginx-deployment
namespace: obivas
spec:
replicas: 10
selector:
matchLabels:
app: nginx-deployment
strategy:
type: RollingUpdate
rollingUpdate:
MaxSurge: 1 ### Pode ter até 1 pod a mais do que eu pedi no arquivo - 11 pods
MaxUnavailable: 2 ### vai atualizar de 2 em 2
template:
metadata:
labels:
app: nginx-deployment
spec:
containers:
- image: nginx:1.16.0
name: nginx
resources:
limits:
cpu: "500m"
memory: 256Mi
requests:
cpu: "300m"
memory: 128Mi
Após executar a criação do deployment usando essa estrategia nosso describe fica assim:
kubectl describe deployments.apps -n obivas nginx-deployment
Name: nginx-deployment
Namespace: obivas
CreationTimestamp: Mon, 27 May 2024 21:04:57 -0300
Labels: app=nginx-deployment
Annotations: deployment.kubernetes.io/revision: 5
Selector: app=nginx-deployment
Replicas: 10 desired | 10 updated | 10 total | 10 available | 0 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 1 max unavailable, 1 max surge
Para após realizar alguma alteração no deploymente para acompanhar o status, usamos o comando
kubectl rollout status deployment -n obivas nginx-deployment
Usando outra estrategia mas menos indicada é a "recreat" essa ela mata td e sobe novamente
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: nginx-deployment
name: nginx-deployment
namespace: obivas
spec:
replicas: 10
selector:
matchLabels:
app: nginx-deployment
strategy:
type: Recreate
template:
metadata:
labels:
app: nginx-deployment
spec:
containers:
- image: nginx:1.16.0
name: nginx
resources:
limits:
cpu: "500m"
memory: 256Mi
requests:
cpu: "300m"
memory: 128Mi
Agora vamos usar o retorno de versão anterior, se na hora de atualzar vc fez cagada, tipo atualizou em prd e era em sandbox, essas coisas, temos o comando.
kubectl rollout undo deployment -n obivas nginx-deployment
deployment.apps/nginx-deployment rolled back
Para saber o que foi alterada
root@obi-System-Product-Name:~/k8s/day3# kubectl rollout history deployment -n obivas nginx-deployment
deployment.apps/nginx-deployment
REVISION CHANGE-CAUSE
6 <none>
8 <none>
9 <none>
Para ver o que foi alterado nas últimas atualização
kubectl rollout history deployment -n obivas nginx-deployment --revision 6
deployment.apps/nginx-deployment with revision #6
Pod Template:
Labels: app=nginx-deployment
pod-template-hash=7b94797f99
Containers:
nginx:
Image: nginx:1.15.0
Port: <none>
Host Port: <none>
Limits:
cpu: 500m
memory: 256Mi
Requests:
cpu: 300m
memory: 128Mi
Environment: <none>
Mounts: <none>
Volumes: <none>
Node-Selectors: <none>
Tolerations: <none>
root@obi-System-Product-Name:~/k8s/day3# kubectl rollout history deployment -n obivas nginx-deployment --revision 8
deployment.apps/nginx-deployment with revision #8
Pod Template:
Labels: app=nginx-deployment
pod-template-hash=86cfc795fc
Containers:
nginx:
Image: nginx:1.17.0
Port: <none>
Host Port: <none>
Limits:
cpu: 500m
memory: 256Mi
Requests:
cpu: 300m
memory: 128Mi
Environment: <none>
Mounts: <none>
Volumes: <none>
Node-Selectors: <none>
Tolerations: <none>
Voltar a uma versão especifica
kubectl rollout history deployment -n obivas nginx-deployment
deployment.apps/nginx-deployment
REVISION CHANGE-CAUSE
11 <none>
12 <none>
13 <none>
root@obi-System-Product-Name:~/k8s/day3# kubectl rollout undo deployment -n obivas nginx-deployment --to-revision=11
deployment.apps/nginx-deployment rolled back
root@obi-System-Product-Name:~/k8s/day3#
kubectl rollout undo deployment -n obivas nginx-deployment --to-revision=6