Question

我已经在GCP上使用kubeadm v1.12成功创建了两个Kubernetes集群并安装了带舵手的nginx-ingress：

helm install stable / nginx-ingress --name nginx-ingress --setrbac.create = true

按照说明，我确认所有nginx-ingress组件均正常工作。

鉴于Service清单nginx-ingress-controller包含以下行类型：spec节末尾的LoadBalancer，我是否应该期望部署会创建GCP LoadBalancer？

如果是这样，我如何找出为什么没有创建LoadBalancer？

我正在使用weave v2.5.0来管理CNI和Docker版本18.06.1-ce

TIA

kubectl describe ingress ingress-nginx
Name:             ingress-nginx
Namespace:        default
Address:          
Default backend:  default-http-backend:80 (<none>)
Rules:
  Host  Path  Backends
  ----  ----  --------
  *       /     nginx:31919 (<none>) 
Annotations:
  kubernetes.io/ingress.class:                nginx
  nginx.ingress.kubernetes.io/ingress.class:  nginx
Events:
  Type    Reason  Age   From                      Message
  ----    ------  ----  ----                      -------
  Normal  CREATE  10s   nginx-ingress-controller  Ingress default/ingress-nginx




kubectl describe pod ingress-nginx-nginx-ingress-controller 
Name:               ingress-nginx-nginx-ingress-controller
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               worker-2/10.240.0.22
Start Time:         Mon, 03 Dec 2018 17:13:53 +0000
Labels:             app=nginx-ingress
                    component=controller
                    pod-template-hash=759bc64cbd
                    release=ingress-nginx
Annotations:        <none>
Status:             Running
IP:                 10.200.128.15
Controlled By:      ReplicaSet/ingress-nginx-nginx-ingress-controller-759bc64cbd
Containers:
  nginx-ingress-controller:
    Container ID:  docker://....
    Image:         quay.io/kubernetes-ingress-controller/nginx-ingress-controller
    Image ID:      docker-pullable://quay.io/kubernetes-ingress-controller/..    
    Ports:         80/TCP, 443/TCP
    Host Ports:    0/TCP, 0/TCP
    Args:
      /nginx-ingress-controller
      --default-backend-service=default/ingress-nginx-nginx-ingress-default
      --election-id=ingress-controller-leader
      --ingress-class=nginx
      --configmap=default/ingress-nginx-nginx-ingress-controller
    State:          Running
      Started:      Mon, 03 Dec 2018 17:13:54 +0000
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:10254/healthz delay=10s timeout=1s
    Readiness:      http-get http://:10254/healthz delay=10s timeout=1s
    Environment:
      POD_NAME:       ingress-nginx-nginx-ingress-controller (v1:metadata.name)
      POD_NAMESPACE:  default (v1:metadata.namespace)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  ingress-nginx-nginx-ingress-token-6sl7l:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  ingress-nginx-nginx-ingress-token-6sl7l
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  5m49s  default-scheduler  Successfully assigned
  Normal  Pulled     5m48s  kubelet, worker-2  Container image
  Normal  Created    5m48s  kubelet, worker-2  Created container
  Normal  Started    5m48s  kubelet, worker-2  Started container

GCP Nginx入口LoadBalancer创建失败

0 个答案: