0

我已经在我的私有 GKE 集群中安装了 Jetstack 证书管理器。一切顺利,但我无法获得颁发的证书。我得到的错误是:

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       1 controller.go:135] cert-manager/controller/challenges "level"=0 "msg"="finished processing work item" "key"="default/[snip]-certificate-2096248848-189663135-2951658629" 
I1101 03:45:25.755400       1 controller.go:129] cert-manager/controller/challenges "level"=0 "msg"="syncing item" "key"="default/[snip]-certificate-2096248848-189663135-2951658629" 
I1101 03:45:25.755810       1 pod.go:58] cert-manager/controller/challenges/http01/selfCheck/http01/ensurePod "level"=0 "msg"="found one existing HTTP01 solver pod" "dnsName"="[snip]" "related_resource_kind"="Pod" "related_resource_name"="cm-acme-http-solver-b6k59" "related_resource_namespace"="default" "resource_kind"="Challenge" "resource_name"="[snip]-certificate-2096248848-189663135-2951658629" "resource_namespace"="default" "type"="http-01" 
I1101 03:45:25.755897       1 service.go:43] cert-manager/controller/challenges/http01/selfCheck/http01/ensureService "level"=0 "msg"="found one existing HTTP01 solver Service for challenge resource" "dnsName"="[snip]" "related_resource_kind"="Service" "related_resource_name"="cm-acme-http-solver-qsvbv" "related_resource_namespace"="default" "resource_kind"="Challenge" "resource_name"="[snip]-certificate-2096248848-189663135-2951658629" "resource_namespace"="default" "type"="http-01" 
I1101 03:45:25.755960       1 ingress.go:91] cert-manager/controller/challenges/http01/selfCheck/http01/ensureIngress "level"=0 "msg"="found one existing HTTP01 solver ingress" "dnsName"="[snip]" "related_resource_kind"="Ingress" "related_resource_name"="cm-acme-http-solver-br7d2" "related_resource_namespace"="default" "resource_kind"="Challenge" "resource_name"="[snip]-certificate-2096248848-189663135-2951658629" "resource_namespace"="default" "type"="http-01" 

这与ClusterIssuer我部署的错误事件相对应:

警告 ErrVerifyACMEAccount 27m (x4 over 28m) cert-manager 无法验证 ACME 帐户:获取https://acme-v02.api.letsencrypt.org/directory:拨号 tcp:i/o 超时

因此,我的资源CertificateRequestCertificate资源永远处于“待定”状态。

这发生在初始集群创建期间。我对证书管理器和入口的配置如下:

apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
  name: letsencrypt-uat
spec:
  acme:
    email: cert-manager+uat@[snip]
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    privateKeySecretRef:
      name: letsencrypt-uat-private-key
    solvers:
    - http01:
        ingress:
          class: nginx
apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
  name: [snip]-uat-certificate
spec:
  secretName: [snip]-uat-tls-cert
  duration: 2160h
  renewBefore: 360h
  commonName: [snip]
  dnsNames:
  - [snip]
  issuerRef:
    name: letsencrypt-uat
    kind: ClusterIssuer
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: [snip]-uat-tls-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: letsencrypt-uat
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/affinity: "cookie"
spec:
  rules:
  - host: [snip]
    http:
      paths:
      - backend:
          serviceName: [snip]-uat-webapp-service
          servicePort: 80
  tls:
  - hosts:
    - [snip]
    secretName: [snip]-uat-tls-cert

我在 GKE 私有集群上,因此也无法运行 webhook 组件。该文档似乎暗示以这种方式运行是可以的,但不建议这样做。

另外,我注意到文档提到需要添加防火墙规则以允许 webhook 工作。我想知道这在这里是否也相关?上面的错误似乎表明某种网络(防火墙?)相关问题。

环境细节:: GKE(1.14.7-gke.10)Kubernetes(v1.16.2)(我认为)cert-manager(0.11.0)

安装有kubectl

我是否需要配置防火墙规则?

非常感谢,本

编辑1:

“拨号 tcp:i/o 超时”是一个红鲱鱼。仅当 DNS 需要使用我的集群进行初始化时,该错误才会持续存在。我也越来越接近结论,传播错误只是 LetsEncrypt DNS 没有看到我的域与我的 IP 地址相关联(还)。

我在这里使用 A 记录是否正确?我大约一个小时前进行了 DNS 更新 - 有什么方法可以让我看到 LetsEncrypt 的 DNS 看到的内容吗?

4

1 回答 1

0

好的,谢谢你们的帮助。事实证明,这与 cert-manager 无关。我在这里遇到了两个问题:

  1. 当时我正在这样做与网络有关的 GCP 问题(这只会引起混乱);
  2. 我的应用程序没有正确响应 HTTP 质询。

但是,最后,出于其他原因,我决定使用 DNS 解析器。这工作得很好。

再次感谢!

于 2019-11-03T04:42:09.697 回答