cert-manager

问题 Im trying to make my google services more secure by moving from http to https. I've been follwing the cert-manager documentation to get it working. https://cert-manager.io/docs/configuration/acme/dns01/google/ I can't install helm on the cluster nor nginx ingress that's why im using the dns01 challenge instead of the http01. I installed cert-manager with regular manifests v0.11.0. After creating a dns admin service account, i used this yaml to create the issuer : apiVersion: cert-manager.io

来源： https://stackoverflow.com/questions/63432101/waiting-on-certificate-issuance-from-order-status-pending

来源： https://stackoverflow.com/questions/60429443/knative-enabling-automatic-tls-certificate-provisioning-not-working

问题 I'm trying to configure HTTPS for my K8s/Istio cluster. I'm following this official tutorial step by step multiple times from scratch and get the same error every time when try to create a Certificate resource. no matches for kind "Certificate" in version "certmanager.k8s.io/v1alpha1" I tried to install cert-manager and its CRD manually based on official docs and no help. cert-manager-5ff755b6d5-9ncgr 1/1 Running 0 6m55s cert-manager-cainjector-576978ffc8-4db4l 1/1 Running 0 6m55s cert

问题 I'm trying to configure HTTPS for my K8s/Istio cluster. I'm following this official tutorial step by step multiple times from scratch and get the same error every time when try to create a Certificate resource. no matches for kind "Certificate" in version "certmanager.k8s.io/v1alpha1" I tried to install cert-manager and its CRD manually based on official docs and no help. cert-manager-5ff755b6d5-9ncgr 1/1 Running 0 6m55s cert-manager-cainjector-576978ffc8-4db4l 1/1 Running 0 6m55s cert

问题 I'm trying to configure HTTPS for my K8s/Istio cluster. I'm following this official tutorial step by step multiple times from scratch and get the same error every time when try to create a Certificate resource. no matches for kind "Certificate" in version "certmanager.k8s.io/v1alpha1" I tried to install cert-manager and its CRD manually based on official docs and no help. cert-manager-5ff755b6d5-9ncgr 1/1 Running 0 6m55s cert-manager-cainjector-576978ffc8-4db4l 1/1 Running 0 6m55s cert

问题 We have a production AKS cluster that has a stable/cert-manager helm chart installed to allow using Let's Encrypt certificates. The current version installed is cert-manager-v0.6.0 in the kube-system namespace. Let's Encrypt is to stop support for traffic from cert-manager pre 8.0 version from 1st of November 2019. I would like to upgrade but the latest available stable chart version is v0.6.7 . Seems like the way to go is to switch to jetstack/cert-manager . How do I best approach this?

问题 I am working with cert-manager in my kubernetes cluster, in order to get certificates signed by let'sencrypt CA to my service application inside my cluster. I am performing the following steps in the order presented. I've wanted provide the most details as a possible of my process in order to understand the behavior presented. Install the CustomResourceDefinition resources separately ⟩ kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.7/deploy/manifests/00

问题 I have installed the Jetstack cert-manager within my private GKE cluster. That all went well, but I can't get a certificate issued. The error that I get is: E1101 03:45:15.754642 1 sync.go:184] cert-manager/controller/challenges "msg"="propagation check failed" "error"="wrong status code '404', expected '200'" "dnsName"="[snip]" "resource_kind"="Challenge" "resource_name"="[snip]-certificate-2096248848-189663135-2951658629" "resource_namespace"="default" "type"="http-01" I1101 03:45:15.755017

问题 I followed https://docs.cert-manager.io/en/venafi/tutorials/quick-start/index.html from start to end and everything seems to be working except that I'm not getting an external ip for my ingress. NAME HOSTS ADDRESS PORTS AGE staging-site-ingress staging.site.io,staging.admin.site.io, 80, 443 1h Altough I'm able to use the nginx ingress controller external ip and use dns to access the sites. When I'm going to the urls I'm being redirected to https, so I assume that's working fine. It redirects