-
Notifications
You must be signed in to change notification settings - Fork 577
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
Cannot connect to insecure private registry #757
Comments
cc @jromero |
@rohitsakala thank you for filing this issue. I've copied this issue to our development repo for this task and added a reply. |
ACME generated certs from cert-manager don't have a ca.crt key. * tektoncd/catalog#757
ACME generated certs from cert-manager don't have a ca.crt key. * tektoncd/catalog#757 Co-authored-by: Mario Manno <[email protected]>
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I am using https://github.com/tektoncd/catalog/blob/master/task/buildpacks/0.3/buildpacks.yaml.
Here the
APP_IMAGE
doesn't take transport style likehttp
orhttps
. Thetekton
staging pod makes anhttps
call to the registry whereas my registry is insecure. How do I telltekton
to make ahttp
request ?The text was updated successfully, but these errors were encountered: