Replies: 1 comment 1 reply
-
It looks like configuring As a workaround, you may create a pre-existing Secret resource. cert-manager will pick up that Secret when creating the Certificate. For example, with the following ClusterIssuer and Ingress (with nginx-ingress): kind: ClusterIssuer
metadata:
name: letsencrypt
spec:
acme:
solvers:
- http01:
ingress:
class: nginx
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: httpbin
annotations:
cert-manager.io/cluster-issuer: letsencrypt
spec:
rules:
- host: mael.pw
http:
paths:
- path: /
pathType: ImplementationSpecific
backend:
service:
name: httpbin
port:
number: 80
tls:
- secretName: httpbin
hosts:
- mael.pw
---
apiVersion: v1
kind: Secret
metadata:
name: httpbin
annotations:
your-annotation: "true" # Your custom annotations. Admittedly, using a pre-existing Secret isn't well documented, but it works really well. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have found this documentation in the values.yaml file of the helm installation.
I am using ClusterIssuer to auto generate Certificates using the
cert-manager.io/cluster-issuer
annotation in the Ingress resource.I understood the
ingress-shim
is responsabile to create this Certificate but I cannot understand how to configureingress-shim
to include thesecretTemplate
section in the Certificate.Has somebody already solved this problem?
Beta Was this translation helpful? Give feedback.
All reactions