Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Trying to uses cert-manager / ingress-shim for the 1st time, but this doesn't works as expected.
I've put my issuer annotation in my Ingress resources file with all my domains to manage.
I've created our issuer, and it's correctly registered.
I've re-installed our application, the cert haven't been created. I've killed the cert-manager pod to force to reload, and the logs of container ingress-shim doesn't seems to have detected/installed the certs.
My issuer and my application are on the same namespace.
What you expected to happen:
Ingress domains should be detected and the certificates should be created.
How to reproduce it (as minimally and precisely as possible):
# ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-http
annotations:
"certmanager.k8s.io/issuer": "imp"
spec:
rules:
- host: my-domain.com
http: &rules
paths:
- backend:
serviceName: my-service
servicePort: 80
- host: www.my-domain.com
http: *rules
---
# issuer.yaml
apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
name: imp
spec:
acme:
server: https://acme-v01.api.letsencrypt.org/directory
email: [email protected]
privateKeySecretRef:
name: imp
http01: {}
Anything else we need to know?:
May be I've missed something in the documentation but I don't see what.
Environment:
kubectl version):# kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:55:54Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration**:
on-premise, Hetzner Cloud
Install tools:
xetys/hetzner-kube
Others:
You need to include a tls stanza in your ingress resource, as per the ingress docs. ingress-shim will then create a Certificate resource that is configured to save the certificate in the secret you have named in your tls stanza 馃槃
Most helpful comment
You need to include a
tlsstanza in your ingress resource, as per the ingress docs. ingress-shim will then create a Certificate resource that is configured to save the certificate in the secret you have named in your tls stanza 馃槃