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 Acme certificate resolver configuration #419

Merged
merged 4 commits into from
May 31, 2022

Conversation

valerauko
Copy link
Contributor

Being able to configure these options via values is much more friendly than having to write it through additionalArgs.

  • added tests for the new values
  • bumped chart version

@@ -349,6 +349,27 @@ persistence:
annotations: {}
# subPath: "" # only mount a subpath of the Volume into the pod

certResolvers: {}
# letsencrypt:
Copy link
Contributor

@jakubhajek jakubhajek Aug 25, 2021

Choose a reason for hiding this comment

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

I think that indention is not correct, there should 2 white spaces instead of 3.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's # (sharp-space) for the comment and two spaces for the indentation.

Other places have a space after the sharp for comments too. Is is a problem?

# # for challenge options cf. https://doc.traefik.io/traefik/https/acme/
# email: email@example.com
# dnsChallenge:
# # also add the provider's required configuration under env
Copy link
Contributor

@jakubhajek jakubhajek Aug 25, 2021

Choose a reason for hiding this comment

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

We have to emphasize that Kubernetes Secret containing DNS provider data is mandatory. Otherwise, a user might be confused about where the sensitive (APK_KEY, login) data should be added.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm a bit confused. How would you rephrase the current comment to be more clear?

@@ -2,7 +2,7 @@ apiVersion: v2
name: traefik
description: A Traefik based Kubernetes ingress controller
type: application
version: 9.19.1
version: 9.19.2
Copy link
Contributor

@jakubhajek jakubhajek Aug 25, 2021

Choose a reason for hiding this comment

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

Would you please update the chart and Traefik version?

Copy link
Contributor

@jakubhajek jakubhajek 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 submitting the PR and adding a user-friendly approach to implement the certResolver feature.

Please review my comments and rebase your branch. Then, I think we are happy to merge it.

@shadycuz
Copy link

shadycuz commented May 29, 2022

@jakubhajek This is a pretty important feature, why dont the maintainers just finish the work that was started?

Copy link
Contributor

@ddtmachado ddtmachado left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants