-
Notifications
You must be signed in to change notification settings - Fork 116
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
NT: Allow the definition of multiple imagePullSecrets. #216
NT: Allow the definition of multiple imagePullSecrets. #216
Conversation
76f14ec
to
d6d2ec1
Compare
Sorry for the multiple failed runs, didn't read the docs enough on building the manifests. |
Was I supposed to add |
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.
Great start!
Would you mind adding a test for this? And also implement the functionality in the prometheusExporter code as well?
The helm chart change is definitely odd. Are you using the kustomize version specified in hack/install_dependencies.sh
?
…ers and sidecarContainers
1a4b8f7
to
d429a8a
Compare
Yep that was the issue, I had an older version installed.
Done!
Sorry this is my first time writing go code, and I'm not familiar with the testing structure. Where should tests for these changes go? |
e5ef571
to
b64bc5c
Compare
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.
Ok the code looks great!
As for the tests, here is some help:
- Where we have been specifying customPodOptions test values.
So you should be able to add a list of ImagePullSecrets here to use other places in the tests. - An example test that you could add in the imagePullSecrets
- Where you would actually test that they got added to the Pod
You can do the same thing for the prometheus exporter tests:
- An example prom-exp test that you could add in the imagePullSecrets
- Where you would actually test that they got added to the prom-exp Pod
These tests aren't actually making sure that it runs correctly, it makes sure that the resulting statefulSet object that is created looks as it should. So you just need to make sure that the pod Template in the statefulset has the correct imagePullSecrets section.
eeae254
to
395e5a5
Compare
Thanks so much for the pointers Houston, let me know if I've missed anything. |
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.
Don't think you've missed anything! This looks great, feature & tests. 👌
Thanks for the contribution! Hopefully the first of many 😉
Currently you can only specify a single imagePullSecret in the ContainerImage, for the SolrImage in SolrCloudSpec. This allows a user to define any number of imagePullSecrets, which is required if initContainers or sidecarContainers need different imagePullSecrets to the SolrImage.