Repository navigation
old pod can be automatically when deployment replica num is updated #7150
Unanswered
AryaCherryLiu
asked this question in
Q&A
Replies: 1 comment
|
Are you incrementing or decrementing the replica count in the deployment? When I tried this with a simple test, incrementing the count from one to two resulted in one additional pod being created. Then when I decremented the count again, the new pod was deleted. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi All,
I Encounter one issue that is:
after update the deployment replica num in my gitops repo, when argocd finished the sync action, the old pod still available, and can't be deleted manually
I want to how to resolve.
Thanks
All reactions