Closed tirumaraiselvan closed 6 years ago
Sounds good but this would be a breaking change. This would change the spec of remote.yaml which means we probably need v1alpha2 group or something?
I think we should go ahead with this for v1alpha1 and make the required changes in v1alpha2
You can create a new key called secretName
and it will not breadk existing config
Either we can go with @shahidhk's suggestion and add this as a non breaking change or bump the version to v1alpha2 and document the changes.
Added secretRef
to point to a secret
Do we need the credentials to have a
secretKeyRef
? Why can't it besecretName
? The controller can then check if the secret's type is one ofkubernetes.io/dockercfg
orkubernetes.io/dockerconfigjson
and act accordingly?