库伯奈特斯集群模式，什么是入口url？

Question

在我有一个vm (centos7.4，主机名Kube-2 2.novalocal，ip 172.50.10.10)之前，我在其中安装了master和kubelet，我可以通过172.50.10.10/uaa/login访问我的入口。在集群中，我使用ClusterIP，并在入口上部署了入口nginx作为NodePort。因为它是重定向/重写，所以我通过避免忽略端口将nodeport更改为80。服务网址是http://172.50.10.10/uaa/login。而且效果很好。

现在我添加两个节点(kube-1.3.novalocal/172.50.10.1和kube-3.3.novalocal/172.50.10.4)。我可以看到入口是由库伯奈特部署在库伯-3。它经常重新启动，几乎每分钟都会重新启动。我也不知道入口服务网址。它是http://kube-2.novalocal/uaa/login or http://kube-3.novalocal/uaa/login?，为什么它重新启动这么频繁？

我把所有相关的yaml文件，日志文件，控制台命令输出和仪表板信息放在这里。

[centos@kube-2 ingress]$ sudo kubectl get po
NAME                                     READY     STATUS    RESTARTS   AGE
gearbox-rack-api-gateway                 1/1       Running   0          15h
gearbox-rack-config-server               1/1       Running   0          15h
gearbox-rack-eureka-server               1/1       Running   0          15h
gearbox-rack-rabbitmq                    1/1       Running   0          15h
gearbox-rack-redis                       1/1       Running   0          15h
gearbox-rack-uaa-service                 1/1       Running   0          15h
gearbox-rack-zipkin-server               1/1       Running   0          15h
ingress-nginx-5c6d78668c-brlsv           1/1       Running   279        15h
nginx-default-backend-6647766887-nbwhl   1/1       Running   0          15h

kube-3.3.novalocal(172.50.10.4)：

[centos@kube-2 ingress]$ curl http://172.50.10.4/uaa/login
curl: (7) Failed connect to 172.50.10.4:80; Connection refused

入口-nginx原木：

[centos@kube-2 ingress]$ sudo kubectl logs ingress-nginx-5c6d78668c-frb2r
-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:    0.15.0
  Build:      git-df61bd7
  Repository: https://github.com/kubernetes/ingress-nginx
-------------------------------------------------------------------------------
W0703 02:16:35.966965       7 client_config.go:533] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0703 02:16:35.967483       7 main.go:158] Creating API client for https://10.96.0.1:443

Dashborad图像如下：

​

​

ingress-nginx-res.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: my-ingress
  namespace: default
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
spec:
  rules:
   - host:
     http:
       paths:
       - path: /
         backend:
           serviceName: gearbox-rack-api-gateway
           servicePort: 5555

ingress-nginx-ctl.yaml

kind: Service
apiVersion: v1
metadata:
  name: ingress-nginx
spec:
  type: NodePort
  selector:
    app: ingress-nginx
  ports:
  - name: http
    port: 80
    nodePort: 80
---
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
  name: ingress-nginx
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: ingress-nginx
    spec:
      terminationGracePeriodSeconds: 60
      serviceAccount: lb
      containers:
      - image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.15.0
        name: ingress-nginx
        imagePullPolicy: Always
        ports:
          - name: http
            containerPort: 80
            protocol: TCP
          - name: https
            containerPort: 443
            protocol: TCP
        livenessProbe:
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 30
          timeoutSeconds: 5
        env:
          - name: POD_NAME
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
          - name: POD_NAMESPACE
            valueFrom:
              fieldRef:
                fieldPath: metadata.namespace
        args:
        - /nginx-ingress-controller
        - --default-backend-service=$(POD_NAMESPACE)/nginx-default-backend 

kubeadm.yaml

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
apiServerExtraArgs:
  service-node-port-range: 80-32767
networking:
  podSubnet: 192.168.0.0/16
kubernetesVersion: v1.10.3
featureGates:
  CoreDNS: true

=================================================

第二版

入口-nginx控制器被更新为0.16.2，与以前的部署相同，入口-nginx几乎每两分钟继续重新启动一次。

NAME                                     READY     STATUS           RESTARTS  AGE
ingress-nginx-59b74f9684-lgm2k           0/1       CrashLoopBackOff   9          20m       192.168.179.5   kube-3.novalocal

​

​

Answer 1

根本原因可能是部署硬件环境。使用我的virtualbox，就不会重新启动。当我使用基于openstack的公司vm时，入口-nginx控制器总是重新启动。

Answer 2

NodePort的使用假定您能够访问所有的豆荚，因此您应该能够同时使用http://kube-2.novalocal/uaa/login和http://kube-3.novalocal/uaa/login。

您可以在这里找到有关NodePort的更多信息：https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types " NodePort :在静态端口( NodePort)上公开每个节点的IP上的服务。将自动创建NodePort服务路由到的ClusterIP服务。您可以通过请求：“从集群外部联系NodePort服务。

关于您的入口- nginx频繁重新启动:尝试升级您的nginx控制器的最新版本，并返回结果。你可以在这里找到它：https://github.com/kubernetes/ingress-nginx

另外，看一看本文中类似的问题：https://github.com/kubernetes/ingress-nginx/issues/2450