-
Notifications
You must be signed in to change notification settings - Fork 143
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
[helm]: implement support for defining image pull secrets #5854
[helm]: implement support for defining image pull secrets #5854
Conversation
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
Looks good.
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.
I think it's more idiomatic to attach these to a ServiceAccount instead of the Pod, but in this case it doesn't matter too much.
Also, can you actually set this in one of the examples?
I don't have a preference of one way (ServiceAccount attachment) over the other (Pod attachment), but since there is this draft PR (planning on working on that soon) that will allow the users to complete override service accounts I chose the latter to deterministically always apply the
I can mention it but having it actually in the example cli commands I don't think so as I don't have a guaranteed elastic-agent image under a private registry and I would like to keep the examples as simple as a straight-forward copy-paste. Would that work or you had something else in mind? |
That's fine. I mostly just want a sanity check that the template works as expected, but for a change as simple as this one it's not that important. |
f36b847
to
4d77360
Compare
Quality Gate passedIssues Measures |
* feat: implement support for defining image pull secrets * doc: add imagePullSecrets in kubernetes default example (cherry picked from commit 053b320) # Conflicts: # deploy/helm/elastic-agent/values.yaml
* feat: implement support for defining image pull secrets * doc: add imagePullSecrets in kubernetes default example (cherry picked from commit 053b320) # Conflicts: # deploy/helm/elastic-agent/values.yaml
What does this PR do?
This PR that adds support for defining
pullImageSecrets
support in the chartWhy is it important?
Users mights need to deploy an agent image from a private repository
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
N/A
How to test this PR locally