Kubernetes Dashboard Ingress从服务器返回空响应

时间:2020-05-19 16:57:20

标签: kubernetes nginx-ingress eks

我正在尝试设置kubernetes仪表板。我已经从我的域启用了自定义ssl证书,并且可以直接卷曲Pod而不出现任何问题-我可以卷曲该服务,并且它也可以正常工作。但是,当我尝试通过入口访问时,我从服务器收到(52)空响应。我有一个NLB转发到Nginx控制器服务的端口(ingress在另一个应用程序中工作正常)。这是我的入口配置:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  labels:
    app: dashboard
    name: dashboard-ingress
  name: dashboard-ingress
  namespace: kubernetes-dashboard
spec:
  rules:
  - host: k8sdash.domain.com
    http:
      paths:
      - backend:
          serviceName: kubernetes-dashboard
          servicePort: 443
        path: /

这是我的入口控制器的Daemonset配置。

apiVersion: apps/v1
kind: DaemonSet
metadata:
  annotations:
    deprecated.daemonset.template.generation: "3"
  creationTimestamp: "2020-05-19T15:48:13Z"
  generation: 3
  labels:
    app: lb
    app.kubernetes.io/component: controller
    chart: nginx-ingress-1.36.3
    heritage: Tiller
    release: lb
  name: lb-controller
  namespace: kube-system
  resourceVersion: "747622"
  selfLink: /apis/apps/v1/namespaces/kube-system/daemonsets/lb-controller
  uid: 19d830ba-f2d9-4c6f-bc8d-d64667a900c7
spec:
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: lb
      release: lb
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: lb
        app.kubernetes.io/component: controller
        component: controller
        release: lb
    spec:
      containers:
      - args:
        - /nginx-ingress-controller
        - --default-backend-service=kube-system/lb-default-backend
        - --publish-service=kube-system/lb-controller
        - --election-id=ingress-controller-leader
        - --ingress-class=nginx
        - --configmap=kube-system/lb-controller
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: lb-controller
        ports:
        - containerPort: 80
          hostPort: 80
          name: http
          protocol: TCP
        - containerPort: 443
          hostPort: 443
          name: https
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources: {}
        securityContext:
          allowPrivilegeEscalation: true
          capabilities:
            add:
            - NET_BIND_SERVICE
            drop:
            - ALL
          runAsUser: 101
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      hostNetwork: true
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: lb
      serviceAccountName: lb
      terminationGracePeriodSeconds: 60
  updateStrategy:
    rollingUpdate:
      maxUnavailable: 1
    type: RollingUpdate
status:
  currentNumberScheduled: 3
  desiredNumberScheduled: 3
  numberAvailable: 3
  numberMisscheduled: 0
  numberReady: 3
  observedGeneration: 3

0 个答案:

没有答案