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.
Create using
helm create cert-manager
initially. Chart.yaml and values.yaml updated for concrete values expected to run cert-manager in a GKE cluster.Update 1/30/25:
Will (subsequent to testing on
gke_hnt-argo-cd_us-central1_argo-cd-cluster-1
cluster) redeploy ClusterIssuer issuers using dns verification which seems to be more impervious to attacks and can support wildcard certs.Once this is deployed by argoCD (cert-manager and Issuers), services should be able to request TLS certs by updating their Ingress resources with appropriate labels (see kuard test service below as an example):