Nginx和Ingress與Kubernetes沒有路由我的請求

Question

我有Docker，Kubernetes（1.7）和Nginx都在我的RHEL7服務器上運行，我自己的服務位於碼頭集裝箱內並被Kubernetes拾起。我知道Kubernetes正在與碼頭工作，因爲我可以使用自己的IP：PORT地址來調用Kubernete吊艙的獲取請求，並且它可以工作。我設置了默認後端的Nginx，並使所有這些工作。我通過調用get pods和get svc命令知道這一點，並且所有事情都按照它應該運行。當我創建入口時，我知道Nginx正在挑選它，因爲當我使用命令kubectl describe pods {NGNIX-CONTROLLER}時，我發現它更新了它的入口，甚至記錄了我命名它的內容。現在我使用kubectl clusterinfo獲得Kubernetes主站的IP地址，並且我使用此IP地址嘗試呼叫我的服務，沿線爲http://KUBEIPADDRESS/PATH/TO/MY/SERVICE，沒有端口號，但不起作用。我不知道發生了什麼事。有人可以幫我解釋爲什麼Ingress和/或Nnginx不能正確地路由到我的服務？我會在下面給我的入口和nginx文件。

（注意，對於nginx的YAML文件中，Nginx的控制器的部署是在底部一路）。

入口YAML

apiVersion: extensions/v1beta1 
kind: Ingress 
metadata: 
    name: gateway-ingress 
    annotations: 
    kubernetes.io/ingress.class: nginx 
    ingress.kubernetes.io/rewrite-target:/
spec: 
    backend: 
    serviceName: default-http-backend 
    servicePort: 80 
    rules: 
    - host: testhost 
    http: 
     paths: 
     - path: /customer 
     backend: 
      serviceName: customer 
      servicePort: 9001 

nginx的控制器YAML

apiVersion: rbac.authorization.k8s.io/v1beta1 
kind: ClusterRole 
metadata: 
    name: ingress 
rules: 
- apiGroups: 
    - "" 
    - "extensions" 
    resources: 
    - configmaps 
    - secrets 
    - services 
    - endpoints 
    - ingresses 
    - nodes 
    - pods 
    verbs: 
    - list 
    - watch 
- apiGroups: 
    - "extensions" 
    resources: 
    - ingresses 
    verbs: 
    - get 
- apiGroups: 
    - "" 
    resources: 
    - events 
    - services 
    verbs: 
    - create 
    - list 
    - update 
    - get 
- apiGroups: 
    - "extensions" 
    resources: 
    - ingresses/status 
    - ingresses 
    verbs: 
    - update 
--- 
apiVersion: rbac.authorization.k8s.io/v1beta1 
kind: Role 
metadata: 
    name: ingress-ns 
    namespace: kube-system 
rules: 
- apiGroups: 
    - "" 
    resources: 
    - pods 
    verbs: 
    - list 
- apiGroups: 
    - "" 
    resources: 
    - services 
    verbs: 
    - get 
- apiGroups: 
    - "" 
    resources: 
    - endpoints 
    verbs: 
    - get 
    - create 
    - update 
--- 
apiVersion: rbac.authorization.k8s.io/v1beta1 
kind: RoleBinding 
metadata: 
    name: ingress-ns-binding 
    namespace: kube-system 
roleRef: 
    apiGroup: rbac.authorization.k8s.io 
    kind: Role 
    name: ingress-ns 
subjects: 
    - kind: ServiceAccount 
    name: ingress 
    namespace: kube-system 
--- 
apiVersion: rbac.authorization.k8s.io/v1beta1 
kind: ClusterRoleBinding 
metadata: 
    name: ingress-binding 
roleRef: 
    apiGroup: rbac.authorization.k8s.io 
    kind: ClusterRole 
    name: ingress 
subjects: 
    - kind: ServiceAccount 
    name: ingress 
    namespace: kube-system 
--- 
apiVersion: extensions/v1beta1 
kind: Deployment 
metadata: 
    name: default-http-backend 
    labels: 
    k8s-app: default-http-backend 
    namespace: kube-system 
spec: 
    replicas: 1 
    template: 
    metadata: 
     labels: 
     k8s-app: default-http-backend 
    spec: 
     terminationGracePeriodSeconds: 60 
     containers: 
     - name: default-http-backend 
     # Any image is permissable as long as: 
     # 1. It serves a 404 page at/
     # 2. It serves 200 on a /healthz endpoint 
     image: gcr.io/google_containers/defaultbackend:1.0 
     livenessProbe: 
      httpGet: 
      path: /healthz 
      port: 8080 
      scheme: HTTP 
      initialDelaySeconds: 30 
      timeoutSeconds: 5 
     ports: 
     - containerPort: 8080 
     resources: 
      limits: 
      cpu: 10m 
      memory: 20Mi 
      requests: 
      cpu: 10m 
      memory: 20Mi 
--- 
apiVersion: v1 
kind: Service 
metadata: 
    name: default-http-backend 
    namespace: kube-system 
    labels: 
    k8s-app: default-http-backend 
spec: 
    ports: 
    - port: 80 
    targetPort: 8080 
    selector: 
    k8s-app: default-http-backend 
--- 
apiVersion: v1 
kind: ServiceAccount 
metadata: 
    name: ingress 
    namespace: kube-system 
--- 
apiVersion: extensions/v1beta1 
kind: Deployment 
metadata: 
    name: nginx-ingress-controller 
    labels: 
    k8s-app: nginx-ingress-controller 
    namespace: kube-system 
spec: 
    replicas: 1 
    template: 
    metadata: 
     labels: 
     k8s-app: nginx-ingress-controller 
    spec: 
     # hostNetwork makes it possible to use ipv6 and to preserve the source IP correctly regardless of docker configuration 
     # however, it is not a hard dependency of the nginx-ingress-controller itself and it may cause issues if port 10254 already is taken on the host 
     # that said, since hostPort is broken on CNI (https://github.com/kubernetes/kubernetes/issues/31307) we have to use hostNetwork where CNI is used 
     # like with kubeadm 
     hostNetwork: true 
     terminationGracePeriodSeconds: 60 
     serviceAccountName: ingress 
     containers: 
     - image: gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.3 
     name: nginx-ingress-controller 
     readinessProbe: 
      httpGet: 
      path: /healthz 
      port: 10254 
      scheme: HTTP 
     livenessProbe: 
      httpGet: 
      path: /healthz 
      port: 10254 
      scheme: HTTP 
      initialDelaySeconds: 10 
      timeoutSeconds: 1 
     ports: 
     - containerPort: 80 
      hostPort: 80 
     - containerPort: 443 
      hostPort: 443 
     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)/default-http-backend 

也當我做kubectl describe ing我得到

Name:     gateway-ingress 
Namespace:    default 
Address: 
Default backend:  default-http-backend:80 (<none>) 
Rules: 
    Host   Path Backends 
    ----   ---- -------- 
    testhost 

       /customer customer:9001 ({IP}:9001,{IP}:9001) 
Annotations: 
    rewrite-target:  /
Events:     <none> 

這裏是我的部署和的情況下，任何人都需要一個

apiVersion: extensions/v1beta1 
kind: Deployment 
metadata: 
    name: customer 
    labels: 
    run: customer 
spec: 
    replicas: 2 
    template: 
    metadata: 
     labels: 
     run: customer 
    spec: 
     containers: 
     - name: customer 
     image: customer 
     imagePullPolicy: Always 
     ports: 
     - containerPort: 9001 
      protocol: TCP 
--- 
kind: Service 
apiVersion: v1 
metadata: 
    name: customer 
spec: 
    selector: 
    run: customer 
    type: NodePort 
    ports: 
    - name: port1 
    protocol: TCP 
    port: 9001 
    targetPort: 9001 

Answer 1

沒有與您設置的一些問題，據我可以看到客戶的服務：

• KUBEIPADDRESS在URL你電話：IP地址不起作用，因爲您配置您的Ingress在testhost上收聽。因此，您需要撥打http://testhost/customer，並將網絡配置爲將testhost解析爲正確的IP地址

• 但是什麼是正確的IP地址？您正嘗試在端口80上使用k8s主設備。如果沒有進一步的配置，這將無法正常工作。爲此，您需要爲Ingress控制器使用一個NodePort服務，該端口在端口80（可能是433）上公開。爲了使用低端口，您需要使用kube-apiserver的選項，請參閱--service-node-port-range on https://kubernetes.io/docs/admin/kube-apiserver/。一旦有效，您可以使用您的k8s羣集的任何節點的任何IP地址作爲testhost。注意：確保沒有其他應用程序在任何節點上使用這些端口！