cert-manager

Wildcard SSL certificate with subdomain redirect in Kubernetes

由 孤者浪人 提交于 2019-12-08 01:32:21
问题 I've configured my Kubernetes to use one wildcard SSL certificate to all my apps using cert-manager and letsencrypt, now the problem is that I can't configure subdomain redirects cause Ingress is kinda "stiff". Here's how I'm trying to achieve this: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: my-wildcard-ingress namespace: mynamespace annotations: kubernetes.io/ingress.class: nginx certmanager.k8s.io/cluster-issuer: letsencrypt-prod certmanager.k8s.io/acme-challenge-type:

Failed to list *v1alpha1.Order: orders.certmanager.k8s.io is forbidden

由 可紊 提交于 2019-12-07 11:26:14
问题 I configured automated SSL certificate management few months ago as described here: http://docs.cert-manager.io/en/latest/tutorials/acme/dns-validation.html for domains: <myhost>.com and dev.<myhost>.com . So I have two namespaces: prod for <myhost>.com and dev for dev.<myhost>.com . In each namespace I have ingress controller and Certificate resource to store certificate to secret. It's working fine and ClusterIssuer automatically updates certificates. But few days ago I tried to add new

Failed to list *v1alpha1.Order: orders.certmanager.k8s.io is forbidden

由 心已入冬 提交于 2019-12-05 16:14:06
I configured automated SSL certificate management few months ago as described here: http://docs.cert-manager.io/en/latest/tutorials/acme/dns-validation.html for domains: <myhost>.com and dev.<myhost>.com . So I have two namespaces: prod for <myhost>.com and dev for dev.<myhost>.com . In each namespace I have ingress controller and Certificate resource to store certificate to secret. It's working fine and ClusterIssuer automatically updates certificates. But few days ago I tried to add new domain: test.<myhost>.com in test namespace with absolutely same configuration of ingress and certificate
订阅 cert-manager