[bitnami/contour] Allow replacing certgen with cert-manager #29416
+108
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
This update introduces a new option,
useCertManager
. When set totrue
, it replaces Contour's certgen with cert-manager by deployingIssuer
andCertificate
resources to issue TLS certificates for communication between Contour and Envoy. The default value isfalse
.Benefits
Cert-manager automates certificate life-cycle management, including renewal before expiration. Certgen, on the other hand, issues certificates with a 1-year validity period and does not support automatic rotation.
Possible drawbacks
Enabling this option introduces a dependency on cert-manager.
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm