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

Add optional kustomize letsencrypt overlay #239

Merged
merged 5 commits into from
Apr 22, 2024

Conversation

LukeRepko
Copy link
Contributor

When using letsencrypt, you must annotate the named ingress with the letsencrypt cluster-issuer as well as any other desired acme.cert-manager.io annotations [1]. As most services have multiple ingresses (external vs internal), we must only annotate the ingress that will be accessed externally, else the ACME solver will not work correctly.

Using this optional overlay will help ensure the expected ingress is annotated. So that the challenge url is accessible externally.

  1. https://cert-manager.io/docs/usage/ingress/#supported-annotations

@LukeRepko LukeRepko marked this pull request as draft April 20, 2024 00:54
Copy link
Contributor

@cloudnull cloudnull left a comment

Choose a reason for hiding this comment

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

I would like to see this accompanied by some docs on the change, otherwise looks great.

When using letsencrypt, you must annotate the named ingress with the
letsencrypt cluster-issuer as well as any other desired
acme.cert-manager.io annotations [1]. As most services have multiple
ingresses (external vs internal), we must only annotate the ingress that
will be accessed externally, else the ACME solver will not work
correctly.

Using this optional overlay will help ensure the expected ingress is
annotated. So that the challenge url is accessible externally.

 1. https://cert-manager.io/docs/usage/ingress/#supported-annotations
The original key paths were incorrect. Not all services use `api` here.
Expand the prod overrides example to include the necessary issuerRef
name of letsencrypt-prod, it is a better fit. Remove the fake cert, key,
and anchors to them.
@LukeRepko LukeRepko force-pushed the letsencrypt branch 2 times, most recently from 14801a5 to 742f483 Compare April 22, 2024 19:53
@LukeRepko LukeRepko marked this pull request as ready for review April 22, 2024 20:25
@LukeRepko LukeRepko requested a review from cloudnull April 22, 2024 20:26
@cloudnull cloudnull merged commit b66d26e into rackerlabs:main Apr 22, 2024
24 checks passed
@LukeRepko LukeRepko deleted the letsencrypt branch April 26, 2024 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants