Introduce kim builder login that works very much like docker login
but instead stores the resulting Docker config.json in a kubernetes
secret in the builder namespace. This secret is rendered to disk in a
temp directory for build operations (to satisfy buildkit) but is
leveraged as an in-memory keyring for shipping auth credentials for
push / pull operations. If the secret setup by the login cli
operation does not exist, kim reverts to the existing behavior of
consulting the ${DOCKER_CONFIG}/config.json for registry credentials.
Introduce
kim builder loginthat works very much likedocker loginbut instead stores the resulting Dockerconfig.jsonin a kubernetes secret in the builder namespace. This secret is rendered to disk in a temp directory forbuildoperations (to satisfy buildkit) but is leveraged as an in-memory keyring for shipping auth credentials forpush/pulloperations. If the secret setup by thelogincli operation does not exist, kim reverts to the existing behavior of consulting the${DOCKER_CONFIG}/config.jsonfor registry credentials.Addresses #64 Fixes #22
Signed-off-by: Jacob Blain Christen jacob@rancher.com