This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
fix: set heapster Deployment to EnsureExists to prevent heapster-nann… #295
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.
…y-induced pod thrashing
Reason for Change:
aks-engine currently delivers a heapster implementation (for clusters < 1.13) that configures the
Deployment
addon toReconcile
, in order to enforce k8s runtime updates to configuration changes from heapster. In practice, folks are experiencing the theheapster-nanny
container is inducing regular reconciliations (read: kill/recreate) of theheapster
pod.This sets the
Deployment
toEnsureExists
instead, which we expect to fix the above symptom; and will require manual reconciliation (read:kubectl delete pod <heapster pod id>
) in order to apply changes to the addon spec.Issue Fixed:
Fixes #275
Requirements:
Notes: