Update imagepullsecrets in service account on existing clusters/serviceaccounts #384
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.
Change log description
Updates the
imagePullSecrets
section of theServiceAccount
on reconciliationWhat the code does
Noticed when working on #383 that if I updated the
imagePullSecrets
setting to use a private repo it wouldn't update theServiceAccount
. This meant I would have to either manually edit theServiceAccount
or delete the cluster and make a new one.This allows updating the
imagePullSecrets
section in theServiceAccount
on existing clusters.Purpose of the change
Fixes #388
How to verify it
Deploy a zookeeper cluster, then update
spec.Pod.ImagePullSecrets
with a new secret and wait for the cluster to reconcile. I also added a unit test covering this use case.