Skip to content
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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

TomBillietKlarrio
Copy link

Fix for #551

@TomBillietKlarrio
Copy link
Author

CI failed, but I doubt it's related to my change. Anybody an idea?

@codecov
Copy link

codecov bot commented May 15, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9fc6151) 85.91% compared to head (fe02e09) 85.91%.

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.
📢 Have feedback on the report? Share it here.

@anishakj
Copy link
Contributor

@TomBillietKlarrio Could you please signoff your commit?

@TomBillietKlarrio TomBillietKlarrio force-pushed the helm-postbuild-credentials branch from 9cf28c4 to fbb7e87 Compare December 14, 2023 12:23
@anishakj anishakj requested a review from jkhalack December 14, 2023 12:30
@anishakj
Copy link
Contributor

@TomBillietKlarrio
Copy link
Author

@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 parts I was touching were only related to the helm-post-intall-upgrade hook parts.

@anishakj
Copy link
Contributor

@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 parts I was touching were only related to the helm-post-intall-upgrade hook parts.

The line no: was not correct, in imagePullsecrets of service account, do we need to check for global value?

@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 parts I was touching were only related to the helm-post-intall-upgrade hook parts.

I meant line no:108, there we are setting imagepullsecret , do we need to consider global imagepullsecret there

@TomBillietKlarrio
Copy link
Author

@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 parts I was touching were only related to the helm-post-intall-upgrade hook parts.

The line no: was not correct, in imagePullsecrets of service account, do we need to check for global value?

@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 parts I was touching were only related to the helm-post-intall-upgrade hook parts.

I meant line no:108, there we are setting imagepullsecret , do we need to consider global imagepullsecret there

I see what you mean, I'll make a patch

@TomBillietKlarrio
Copy link
Author

@anishakj I believe the PR is ready

@@ -10,6 +15,11 @@ triggerRollingRestart: false

domainName:
labels: {}

Copy link
Contributor

@anishakj anishakj Jan 9, 2024

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

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

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

Copy link
Contributor

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?

@anishakj
Copy link
Contributor

@jkhalack Could you please have a look at this PR

Comment on lines -110 to +112
{{ toYaml .Values.pod.imagePullSecrets | indent 6 }}
{{- range (default .Values.global.imagePullSecrets .Values.pod.imagePullSecrets) }}
- name: {{ . }}
{{- end }}
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants