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

Hubble-ui now supports imagePullSecrets #15109

Merged
merged 1 commit into from
Mar 1, 2021
Merged

Conversation

domgoodwin
Copy link
Contributor

@domgoodwin domgoodwin commented Feb 25, 2021

Currently there is no way to specify pull secrets for the hubble ui deployment.

Hubble-ui now supports imagePullSecrets being passed in

@domgoodwin domgoodwin requested a review from a team as a code owner February 25, 2021 12:30
@domgoodwin domgoodwin requested review from a team and kaworu February 25, 2021 12:30
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Feb 25, 2021
@domgoodwin domgoodwin requested a review from brb February 25, 2021 12:30
@sayboras sayboras added area/helm Impacts helm charts and user deployment experience release-note/minor This PR changes functionality that users may find relevant to operating Cilium. labels Feb 25, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Feb 25, 2021
Copy link
Member

@sayboras sayboras left a comment

Choose a reason for hiding this comment

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

Thanks for your PR, changes lgtm once CI build is passed.

imagePullSecrets sets every other pod's containers to use the set secrets but currently not hubble-ui, this will add the same code the cilium daemonset and operators use to ensure pulling from private registries works.

Signed-off-by: Dom Goodwin <[email protected]>
{{- end }}
{{- if .Values.imagePullSecrets }}
imagePullSecrets:
{{ toYaml .Values.imagePullSecrets | indent 6 }}
Copy link
Member

Choose a reason for hiding this comment

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

Any reason this is formatted differently than the tolerations: L41? Shouldn't this be indented to 8 instead of 6?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was basing it off: https://github.com/cilium/cilium/blob/master/install/kubernetes/cilium/templates/cilium-agent-daemonset.yaml#L88

As it's an array 6 indentation is still valid but happy to change to 8 if preferred

      imagePullSecrets:
      - item
      
      imagePullSecrets:
        - item

Copy link
Member

Choose a reason for hiding this comment

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

Thank you, I see that we indent imagePullSecrets inconsistently across the different Helm template, but that's outside the scope of this PR.

@kaworu
Copy link
Member

kaworu commented Feb 26, 2021

test-me-please

Edit: K8s 1.20 kernel 4.9 hit #15132

@christarazi
Copy link
Member

retest-1.20-4.9

@aanm aanm merged commit 9282087 into cilium:master Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm Impacts helm charts and user deployment experience release-note/minor This PR changes functionality that users may find relevant to operating Cilium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants