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
Description of the issue:
One task encountered is to build images, push images, and run these deploy these images on Kubernetes at runtime.
Problem: DockerConfigCredentialRetriever.java is sufficient for setups where the authentication token is not changed. But not sufficient for a setup with rolling keys. So, once a given docker-registry secret changes, this means a volume with the given secret needs to be re-mounted / the pod restarted.
Expected behavior:
It would be great to have an implementation KubernetesConfigCredentialRetriever.java, which either links to a ServiceAccount or new KubernetesConfigCredentialRetriever(String kubernetesSecret) instance to retrieve the credentials from a local secret.
The text was updated successfully, but these errors were encountered:
@HknLof There are a number of ways in which Jib gathers credentials. One of the ways is through reading the $HOME/.docker/config.json file. As described in this suggestion by @chanseokoh, if you follow the steps to mount a secret in a volume and copy/symlink the file to $HOME/.docker/config.json then that can be picked up by Jib.
@mpeddada1 thank you for the information. That, is how I am working with Jib right now. For now, this is sufficient. Probably we will have our own CredentialProvider for the use case, where registry tokens might change. Thanks, for the fast reply :)
Environment:
Kubernetes 1.21
jib-core-0.20.0
Description of the issue:
One task encountered is to build images, push images, and run these deploy these images on Kubernetes at runtime.
Problem:
DockerConfigCredentialRetriever.java
is sufficient for setups where the authentication token is not changed. But not sufficient for a setup with rolling keys. So, once a givendocker-registry
secret changes, this means a volume with the given secret needs to be re-mounted / the pod restarted.Expected behavior:
It would be great to have an implementation
KubernetesConfigCredentialRetriever.java
, which either links to aServiceAccount
ornew KubernetesConfigCredentialRetriever(String kubernetesSecret)
instance to retrieve the credentials from a local secret.The text was updated successfully, but these errors were encountered: