-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 551: allow helm imagePullSecrets on post-install hook #554
base: master
Are you sure you want to change the base?
Issue 551: allow helm imagePullSecrets on post-install hook #554
Conversation
CI failed, but I doubt it's related to my change. Anybody an idea? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #554 +/- ##
=======================================
Coverage 85.91% 85.91%
=======================================
Files 12 12
Lines 1633 1633
=======================================
Hits 1403 1403
Misses 145 145
Partials 85 85 ☔ View full report in Codecov by Sentry. |
@TomBillietKlarrio Could you please signoff your commit? |
Signed-off-by: Tom Billiet <[email protected]>
Signed-off-by: Tom Billiet <[email protected]>
Signed-off-by: Tom Billiet <[email protected]>
Signed-off-by: Tom Billiet <[email protected]>
9cf28c4
to
fbb7e87
Compare
Signed-off-by: Tom Billiet <[email protected]>
@TomBillietKlarrio Does it require similar change in https://github.com/pravega/zookeeper-operator/blob/master/charts/zookeeper/templates/zookeeper.yaml#L107 |
I'm not quite sure what you mean here. This line refers to the serviceAccount of the zookeeper itself, which gets created by the zookeeper-operator itself I believe. |
The line no: was not correct, in
I meant line no:108, there we are setting |
I see what you mean, I'll make a patch |
Signed-off-by: Tom Billiet <[email protected]>
Signed-off-by: Tom Billiet <[email protected]>
@anishakj I believe the PR is ready |
@@ -10,6 +15,11 @@ triggerRollingRestart: false | |||
|
|||
domainName: | |||
labels: {} | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Below code block is not required looks like, service account is mentioned at line no:56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is. It's used here:
https://github.com/klarrio-kpn-dsh/zookeeper-operator/blob/fe02e094a4c2f640dbecd56d4424cc1b58c86d25/charts/zookeeper/templates/post-install-upgrade-hooks.yaml#L41
And in line with the zookeeper-operator
values:
https://github.com/klarrio-kpn-dsh/zookeeper-operator/blob/fe02e094a4c2f640dbecd56d4424cc1b58c86d25/charts/zookeeper-operator/values.yaml#L27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
referring zookeeper/values.yaml not the zookeeper-operator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 56 here has pod.imagePullSecrets
(used on ZookeeperCluster resource).
The proposed addition would specify serviceAccount.imagePullSecrets
(to be used on the hooks).
@TomBillietKlarrio Why don't we move this to hooks.serviceAccount.imagePullSecrets
to make it clear that the particular set of pull secrets would be pertinent to the hook image docker registry?
@jkhalack Could you please have a look at this PR |
{{ toYaml .Values.pod.imagePullSecrets | indent 6 }} | ||
{{- range (default .Values.global.imagePullSecrets .Values.pod.imagePullSecrets) }} | ||
- name: {{ . }} | ||
{{- end }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would constitute a breaking change. Do we have grounds for it?
The schema for .Values.pod.imagePullSecrets
seems to require an array of key-value pairs, while proposed schema for .Values.global.imagePullSecrets
seems to an array of strings.
Fix for #551