You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, it'd be great if DOCKERCFGSECRET was harmonized with the format that is created by kubectl and added an the auth field to the secret that is created in k8s, while not necessary for the the secret to work with kubernetes for image pulls, some external tools like Weavework's flux expect it to exist(fluxcd/flux#1596).
In the 1.13.0 release of kubectl they had also stripped out the auth field, but then re-added it in kubernetes/kubernetes#72344
The text was updated successfully, but these errors were encountered:
Hey, it'd be great if
DOCKERCFGSECRET
was harmonized with the format that is created by kubectl and added an theauth
field to the secret that is created in k8s, while not necessary for the the secret to work with kubernetes for image pulls, some external tools like Weavework's flux expect it to exist(fluxcd/flux#1596).In the
1.13.0
release ofkubectl
they had also stripped out theauth
field, but then re-added it in kubernetes/kubernetes#72344The text was updated successfully, but these errors were encountered: