Restart deployments depending on cluster config during cx configure #2367
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deliahu
approved these changes
Jul 23, 2021
manager/install.sh
Outdated
Comment on lines
284
to
285
| kubectl scale deployment operator-controller-manager --replicas=0 - >/dev/null | ||
| kubectl scale deployment operator-controller-manager --replicas=1 - >/dev/null |
Member
There was a problem hiding this comment.
For restarting the operator pod, we delete the pod and let the deployment bring it back:
kubectl -n=default delete --ignore-not-found=true --grace-period=10 deployment operator >/dev/null 2>&1Is there a reason you went with kubectl scale, and if so, should we change that one too?
deliahu
approved these changes
Jul 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
checklist:
make testandmake lint