When serviceAccount.create is true, this chart creates
a service account. Currently, that service account will be
created without an explicit namespace. This can be problematic
because the Deployment resource does have an explicit namespace
set. Because the ServiceAccount and Deployment (ultimately, the
Pod) must coexist in the same namespace, we need to follow the
same logic when setting the namespace for both.
When
serviceAccount.createistrue, this chart creates a service account. Currently, that service account will be created without an explicit namespace. This can be problematic because the Deployment resource does have an explicit namespace set. Because the ServiceAccount and Deployment (ultimately, the Pod) must coexist in the same namespace, we need to follow the same logic when setting the namespace for both.Intended to fix https://github.com/twuni/docker-registry.helm/issues/60.
See https://github.com/twuni/docker-registry.helm/blob/main/templates/deployment.yaml#L5 and https://github.com/twuni/docker-registry.helm/blob/main/templates/secret.yaml#L5 for reference on how the namespace is being set in these other resources.