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
This is a correction request in kubernetes documentation
Feature Request
[ X] Bug Report
Kubernetes documentation on pull-image-private-registry should be updated as docker config has different json response than what is mentioned in document:
**Kubernetes imagePullSecret doesn't support new docker config i.e. it doesn't support config with {"auths":..} object. **
It looks like there was a problem with the registry secret type and datakey in kubectl 1.9.0 (see kubernetes/kubernetes#57427 (comment) for more info and for workaround for 1.9.0), and fixed in 1.9.1. From what I can tell, the 'auths' element in the docs json representation is correct, however there are some other changes related to the 'regsecret' yaml example and the .dockercfg (now .dockerconfigjson) json output.
I've addressed these corrections in #7248
Hopefully that resolves the issue.
This is a correction request in kubernetes documentation
Kubernetes documentation on pull-image-private-registry should be updated as docker config has different json response than what is mentioned in document:
**Kubernetes imagePullSecret doesn't support new docker config i.e. it doesn't support config with {"auths":..} object. **
Page to Update:
https://kubernetes.io/editdocs/#docs/tasks/configure-pod-container/pull-image-private-registry.md
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
The text was updated successfully, but these errors were encountered: