DescomplicandoKubernetes - 3 (Update README.md) - add new information about rollback #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nos meus estudos tive uma duvida que foi sanada na mesma aula do treinamento DescomplicandoKubernetes ...
Pessoal, quando estava fazendo a aula (Fazendo Rollback e conhecendo o comando Rollout) no minuto 2:40 o @badtuxx fez o rollback do deployment (kubectl rollout undo deployment -n giropops nginx-deployment) para voltar para o deploy anterior.
No primeiro momento eu pensei que o "rollout undo" faria o rollback do "Deploy Inteiro", porem no minuto 4:02, ao fazer o describe mostrou que as alterações feitas nas informações do Deploy ( como as Labels e as Replicas) permaneceram.
No minuto 6:17 que eu entendi que na verdade o rollout cuida somente das configurações a nivel de Pod.
Achei valido trazer essa informação porque me foi muito importante.
na Documentação está sendo falado dobre isso... atente a Nota:
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-back-a-deployment