admin管理员组

文章数量:1406937

I'm using GKE with an Ingress and a ManagedCertificate for my domain (details redacted). My YAML manifest is as follows:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-name-ingress
  annotations:
    kubernetes.io/ingress.global-static-ip-name: 'My static Ip' 
    networking.gke.io/managed-certificates: gke-managed-cert
    kubernetes.io/ingress.allow-http: 'true' 
spec:
  rules:
    - host: my.host
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: nodejs-api-service
                port:
                  number: 80

I’ve Verified:

  • DNS: nslookup example returns the expected public IP.
  • Forwarding Rules: A rule exists with the same public IP.
  • Ingress: kubectl get ingress my-ingress -o wide shows no external IP.
  • ManagedCertificate: It remains in "Provisioning" with domain status "FailedNotVisible".

What could cause the Ingress to not display an external IP and the ManagedCertificate to remain "FailedNotVisible," and what steps should I take next?

本文标签：

版权声明：本文标题：ssl certificate - GKE ManagedCertificate "FAILED_NOT_VISIBLE" & Missing Ingress External IP - Stack Ov 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1744971845a2635281.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。