GKE 中缺少 Kubernetes 入口地址

Question

我已经从 ingress 安装了所需的 K8 控制器，但是在执行 kubectl delete all --all 后，它似乎删除了一些我不应该删除的东西。

缺少地址的输出：

my-ingress   <none>   *                 80      15m

INgress 文件：

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-ingress
spec:
  rules:
  - http:
      paths:
      - path: /*
        pathType: ImplementationSpecific
        backend:
          service:
            name: questionbankrestapi
            port:
              number: 80
      - path: /discounted
        pathType: ImplementationSpecific
        backend:
          service:
            name: questionbankrestapi
            port:
              number: 80

我已经使用以下方式安装了 GKE 控制器：

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.1/deploy/static/provider/cloud/deploy.yaml

而且我还完成了绑定：

kubectl create clusterrolebinding cluster-admin-binding   --clusterrole cluster-admin   --user $(gcloud config get-value account)

这是描述输出：

Name:             my-ingress
Labels:           <none>
Namespace:        default
Address:          
Default backend:  default-http-backend:80 (10.4.0.6:8080)
Rules:
  Host        Path  Backends
  ----        ----  --------
  *           
              /*            questionbankrestapi:80 (10.4.0.10:4000)
              /discounted   questionbankrestapi:80 (10.4.0.10:4000)
Annotations:  <none>
Events:
  Type     Reason  Age                 From                     Message
  ----     ------  ----                ----                     -------
  Normal   Sync    84s (x4 over 20m)   loadbalancer-controller  Scheduled for sync
  Warning  Sync    83s (x20 over 19m)  loadbalancer-controller  Error syncing to GCP: error running backend syncing routine: error ensuring health check: googleapi: Error 400: Invalid value for field 'resource.timeoutSec': '15'. TimeoutSec should be less than checkIntervalSec., invalid

Kubernetes 版本：

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3", GitCommit:"816c97ab8cff8a1c72eccca1026f7820e93e0d25", GitTreeState:"clean", BuildDate:"2022-01-25T21:25:17Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.6-gke.1503", GitCommit:"2c7bbda09a9b7ca78db230e099cf90fe901d3df8", GitTreeState:"clean", BuildDate:"2022-02-18T03:17:45Z", GoVersion:"go1.16.9b7", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.23) and server (1.21) exceeds the supported minor version skew of +/-1

Ran the Ready Check，似乎也可以：

+]ping ok
[+]log ok
[+]etcd ok
[+]informer-sync ok
[+]poststarthook/start-kube-apiserver-admission-initializer ok
[+]poststarthook/generic-apiserver-start-informers ok
[+]poststarthook/priority-and-fairness-config-consumer ok
[+]poststarthook/priority-and-fairness-filter ok
[+]poststarthook/start-apiextensions-informers ok
[+]poststarthook/start-apiextensions-controllers ok
[+]poststarthook/crd-informer-synced ok
[+]poststarthook/bootstrap-controller ok
[+]poststarthook/rbac/bootstrap-roles ok
[+]poststarthook/scheduling/bootstrap-system-priority-classes ok
[+]poststarthook/priority-and-fairness-config-producer ok
[+]poststarthook/start-cluster-authentication-info-controller ok
[+]poststarthook/aggregator-reload-proxy-client-cert ok
[+]poststarthook/start-kube-aggregator-informers ok
[+]poststarthook/apiservice-registration-controller ok
[+]poststarthook/apiservice-status-available-controller ok
[+]poststarthook/kube-apiserver-autoregistration ok
[+]autoregister-completion ok
[+]poststarthook/apiservice-openapi-controller ok
[+]shutdown ok
readyz check passed

Answer 1

如果您运行 kubectl delete all --all 命令，那么您就删除了当前命名空间中的所有内容，例如 Pod、Services 和 Statefulsets，但是 RoleBindings、ServiceAccounts 和NetworkPolicies 不是。

因此，我建议您验证您的负载均衡器服务和您的 <一个href="https://cloud.google.com/load-balancing/docs/health-checks?_ga=2.150253750.-1418735072.1639493729&_gac=1.582 31512.1644874296.Cj0KCQiAmKiQBhClarisAKtSj-lB_WBXa-9wl6d_L82biDdigqRuRUo73tv-hc_H_VnoZyQZsQoCb3MaAix5EALw_wcB#list-hcs" rel="nofollow noreferrer">健康检查时间值设置为15秒；这是默认值。 如果是，请设置为60秒，因为超时值必须小于或等于间隔。此外，如果入口已被删除；这也可能是服务 IP 不显示的原因。

您可以在服务和服务中查看此内容。 Kubernetes Engine GCP 控制台菜单中的 ingress 选项，因此如果已删除，请尝试重新创建入口 从头开始。

下面附上如何正确设置后端配置健康检查的示例：

    healthCheck:
    checkIntervalSec: 10
    timeoutSec: 10
    port: 80
    requestPath: /discounted
    type: HTTPS
    securityPolicy:
    name: your-policy-restricted
    sessionAffinity:
    affinityType: NONE
    timeoutSec: 60