kubernetes-ingress

来源： https://stackoverflow.com/questions/63597967/nginx-ingress-rewrite-target-breaks-link-to-net-core-api

来源： https://stackoverflow.com/questions/57868848/problems-configuring-ingress-with-cookie-affinity

来源： https://stackoverflow.com/questions/57868848/problems-configuring-ingress-with-cookie-affinity

问题 We try to implement WebSocket on the Kubernetes cluster using nginx-ingress controller. ingress.yaml: apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/proxy-read-timeout: "7200" ingress.kubernetes.io/proxy-send-timeout: "7200" kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/backend-protocol: HTTPS generation: 2 labels: app: websocket app.kubernetes.io/managed-by: Helm chart: websocket-0.2.2693 release: websocket name: websocket namespace

问题 We try to implement WebSocket on the Kubernetes cluster using nginx-ingress controller. ingress.yaml: apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/proxy-read-timeout: "7200" ingress.kubernetes.io/proxy-send-timeout: "7200" kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/backend-protocol: HTTPS generation: 2 labels: app: websocket app.kubernetes.io/managed-by: Helm chart: websocket-0.2.2693 release: websocket name: websocket namespace

问题 We try to implement WebSocket on the Kubernetes cluster using nginx-ingress controller. ingress.yaml: apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/proxy-read-timeout: "7200" ingress.kubernetes.io/proxy-send-timeout: "7200" kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/backend-protocol: HTTPS generation: 2 labels: app: websocket app.kubernetes.io/managed-by: Helm chart: websocket-0.2.2693 release: websocket name: websocket namespace

问题 I need to configure Ingress Nginx on azure k8s, and my question is if is possible to have ingress configured in one namespace et. ingress-nginx and some serivces in other namespace eg. resources? My files looks like so: # ingress-nginx.yaml apiVersion: extensions/v1beta1 kind: Deployment metadata: name: nginx-ingress-controller namespace: ingress-nginx spec: replicas: 3 selector: matchLabels: app: ingress-nginx template: metadata: labels: app: ingress-nginx annotations: prometheus.io/port:

问题 paths: - backend: serviceName: booknotes-front-end-service servicePort: 80 path: / - backend: serviceName: booknotes-back-end-service servicePort: 3000 path: /api Here is a rules in my ingres-nginx resource . I try to direct all traffic which starts from /api to my back end service, which works properly, but if some route in my back end will be like /api/users it doesn't work , my back end send response not found , when I run it locally this route working properly. Also I've tried delete /api

问题 paths: - backend: serviceName: booknotes-front-end-service servicePort: 80 path: / - backend: serviceName: booknotes-back-end-service servicePort: 3000 path: /api Here is a rules in my ingres-nginx resource . I try to direct all traffic which starts from /api to my back end service, which works properly, but if some route in my back end will be like /api/users it doesn't work , my back end send response not found , when I run it locally this route working properly. Also I've tried delete /api

问题 I want to create a Internal Ingress for my GKE workloads. I want to know what is the annotation that I can use so that I set a static INTERNAL IP address/name in my ingress. apiVersion: extensions/v1beta1 kind: Ingress metadata: name: ingress-https namespace: istio-system annotations: kubernetes.io/ingress.allow-http: "false" kubernetes.io/ingress.class: "gce-internal" ingress.gcp.kubernetes.io/pre-shared-cert: my-cert helm.sh/chart: {{ include "devtools.chart" . }} app.kubernetes.io/instance