Skip to content
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

Fix ingress annotation and cert-manager configuration 👼 #152

Merged
merged 1 commit into from
Dec 11, 2019

Conversation

vdemeester
Copy link
Member

Changes

This is what was required (with some crazy, not useful hack on my part
😹) to fix https on prow.tekton.dev

As follow-up, we need a little bit more docs/link to help debug potential problems 👼

Signed-off-by: Vincent Demeester vdemeest@redhat.com

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 11, 2019
@@ -7,8 +7,8 @@ spec:
email: dlorenc@google.com
privateKeySecretRef:
name: letsencrypt-prod
server: https://acme-staging-v02.api.letsencrypt.org/directory
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was problematic as the generated cert was fake

@@ -2,7 +2,7 @@ apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
cert-manager.io/acme-http01-edit-in-place: "true"
acme.cert-manager.io/acme-http01-edit-in-place: "true"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was blocking the actual cert generation as cert-manager was trying to create an additionnal ingress and thus, the HTTP challenge was always 404

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be acme.cert-manager.io/http01-edit-in-place: "true" ?
https://cert-manager.io/docs/tutorials/acme/ingress/

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes.. I forgot to push my last change 😂

@vdemeester
Copy link
Member Author

I think it really fixed it 👼
/meow

/cc @bobcatfish @dibyom

@tekton-robot
Copy link
Contributor

@vdemeester: cat image

In response to this:

I think it really fixed it 👼
/meow

/cc @bobcatfish @dibyom

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.

Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this!
One question before it's merged.

@@ -2,7 +2,7 @@ apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
cert-manager.io/acme-http01-edit-in-place: "true"
acme.cert-manager.io/acme-http01-edit-in-place: "true"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be acme.cert-manager.io/http01-edit-in-place: "true" ?
https://cert-manager.io/docs/tutorials/acme/ingress/

This is what was required (with some crazy, not useful hack on my part
😹) to fix https on prow.tekton.dev

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 11, 2019
@dlorenc
Copy link
Contributor

dlorenc commented Dec 11, 2019

/lgtm

Whoops!

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 11, 2019
Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!
/lgtm
/approve

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli, dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot merged commit 3ce0b82 into tektoncd:master Dec 11, 2019
@vdemeester vdemeester deleted the fix-ingress-cert-manager branch December 11, 2019 15:20
@vdemeester vdemeester mentioned this pull request Dec 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants