Conversation
326b6a7
to
d572ecb
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.
Looking good. The one thing I noticed is that the value is defined as an array, but all of the tests only test a single value. It'd be good to make sure that the iteration through multiple values works as expected too.
values.yaml
Outdated
# | ||
# Example: | ||
# imagePullSecrets: | ||
# - name: my-secret-name |
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.
These example feels confusing. When empty, the value needs []
, but it doesn't need them when I give a value? In the extraConfig
text we mention that it's an array of objects, which might help a bit.
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.
Yeah good call, changed to say "array of objects containing image pull secret names"
d572ecb
to
b368041
Compare
For sure. I've changed the tests to set two image pull secrets and assert that both are set. |
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.
Generally when we're testing for several values, each one is checked separately. Example: env variable
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.
One more question-- should these be quoted? From the docs, it looks like they're not being quoted:
imagePullSecrets:
- name: myregistrykey
It doesn't matter, it's just a string. |
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.
Though if the quoting doesn't matter, it's a little odd to go to the effort to add it.
Yeah I'll remove it. |
Allow configuring image pull secrets via service account. To use, set the helm config global: imagePullSecrets: - name: my-secret-with-image-pull-secrets
bbdd9ff
to
5eea9ca
Compare
Allow setting image pull secrets for service accounts to enable pulling the consul-k8s and consul images from private registries.
Kube docs: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account
Notes
imagePullSecrets
to DaemonSets #270