在IKS上执行AppID之后，入口不会重定向到我的服务

Question

我有一个绑定了AppID的IKS集群。我在重定向带有入口的NodeJS应用程序时遇到了问题。所有其他应用程序都可以与AppID和ingress一起使用，但这个应用程序在从AppID重定向时提供了500 Internal Server error。当该服务用作NodePort并通过服务器地址和该nodePort进行访问时，该服务工作得很好。

在描述入口时，我只能得到成功的结果

Events:
  Type    Reason   Age    From                                                             Message
  ----    ------   ----   ----                                                             -------
  Normal  Success  58m    public-cr9c603a564cff4a27adb020dd40ceb65e-alb1-59fb8fc894-s59nd  Successfully applied ingress resource.

我的入口看起来像：

apiVersion: v1
items:
- apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      ingress.bluemix.net/appid-auth: bindSecret=binding-raven3-app-id namespace=default
        requestType=web serviceName=r3-ui
      ingress.bluemix.net/rewrite-path: serviceName=r3-ui rewrite=/;
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{"ingress.bluemix.net/appid-auth":"bindSecret=binding-raven3-app-id namespace=default requestType=api serviceName=r3-ui [idToken=false]"},"name":"myingress","namespace":"default"},"spec":{"rules":[{"host":"*host*","http":{"paths":[{"backend":{"serviceName":"r3-ui","servicePort":3000},"path":"/"}]}}],"tls":[{"hosts":["mydomain"],"secretName":"mytlssecret"}]}}
    creationTimestamp: "2019-06-20T10:31:57Z"
    generation: 21
    name: myingress
    namespace: default
    resourceVersion: "24140"
    selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/myingress
    uid: a15f74aa-9346-11e9-a9bf-f63d33811ba6
  spec:
    rules:
    - host: *host*
      http:
        paths:
        - backend:
            serviceName: r3-ui
            servicePort: 3000
          path: /
    tls:
    - hosts:
      - *host*
      secretName: raven3
  status:
    loadBalancer:
      ingress:
      - ip: 169.51.71.141
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

我的服务如下所示：

apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2019-06-20T09:25:30Z"
  labels:
    app: r3-ui
    chart: r3-ui-0.1.0
    heritage: Tiller
    release: r3-ui
  name: r3-ui
  namespace: default
  resourceVersion: "23940"
  selfLink: /api/v1/namespaces/default/services/r3-ui
  uid: 58ff6604-933d-11e9-a9bf-f63d33811ba6
spec:
  clusterIP: 172.21.180.240
  ports:
  - name: http
    port: 3000
    protocol: TCP
    targetPort: http
  selector:
    app: r3-ui
    release: r3-ui
  sessionAffinity: None
  type: ClusterIP
status:

奇怪的是，我在端口80和端口443上得到了不同的结果。在端口80上，我收到HTTP error 500；在端口443上，我收到Invalid Host header

Answer 1

您是否使用https来访问您的应用程序？出于安全原因，App ID身份验证仅支持启用了TLS/SSL的后端。

如果您正在使用SSL，但仍然有问题，您是否可以分享您的入口和应用程序日志，以便我们可以找出哪里出了问题？

谢谢。