-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to resolve images in unauthenticated registries #143
Labels
Comments
matthewmcnew
added a commit
that referenced
this issue
Sep 30, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
Merged
matthewmcnew
added a commit
that referenced
this issue
Sep 30, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Sep 30, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Sep 30, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Sep 30, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
matthewmcnew
added a commit
that referenced
this issue
Oct 1, 2019
- Allow auth for images to be fetched via kubernetes/credentialprovider - Allow images/builds to be built with unauthenticated registries - Resolves #143 - Remove ImageRef interface - Images are fetched with concrete SecretRef - Builder auth can be fetched with default service account imagePullSecrets
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Building an image targeting an unauthenticated registry completed the builds and published the image to the registry, however, the kpack-controller errors when it is unable to find a secret for that registry (there shouldn't be one). This results in the build's ready condition never becoming true.
Here's what I see in the kpack-controller log with v0.0.4. In this case,
registry.kube-system.svc.cluster.local
is also an insecure registry, but I doubt that's what's causing issues.The text was updated successfully, but these errors were encountered: