kubernetes-ingress

问题 Recently I've been working on a toy app using Kubernetes. Part of the app is a web server that needs to support WebSockets. Currently, I'm using port-forwarding to access the web server and everything works just fine. I'd like to switch to using an Ingress and IngressController to avoid using the port forwarding. Here is my Ingress config: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: app-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: / nginx.ingress

问题 The IP whitelisting/blacklisting example explained here https://kubernetes.io/docs/tutorials/services/source-ip/ uses source.ip attribute. However, in kubernetes (kubernetes cluster running on docker-for-desktop) source.ip returns the IP of kube-proxy. A suggested workaround is to use request.headers["X-Real-IP"] , however it doesn't seem to work and returns kube-proxy IP in docker-for-desktop in mac. https://github.com/istio/istio/issues/7328 mentions this issue and states: With a proxy that

问题 I am trying to add multiple Ingresses which should share the same host. One Ingress should handle requests to www.example.de/some and the one all other requests. Here is a snipped with the Ingress configurations apiVersion: extensions/v1beta1 kind: Ingress metadata: name: some-ingress annotations: kubernetes.io/ingress.class: "nginx" spec: rules: - host: "www.example.de" http: paths: - path: "/some" backend: serviceName: some-svc servicePort: 8585 apiVersion: extensions/v1beta1 kind: Ingress

问题 I'm trying to find a solution for the problem that seems like something very common. I have a k8s cluster ip service which exposes two ports: 8088 and 60004 I would like to expose these same ports on ALB and not use path based routing This works for exposing one service on 8088 port: --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myingress namespace: myns annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/healthcheck-path: /ping alb.ingress.kubernetes.io

问题 I'm trying to find a solution for the problem that seems like something very common. I have a k8s cluster ip service which exposes two ports: 8088 and 60004 I would like to expose these same ports on ALB and not use path based routing This works for exposing one service on 8088 port: --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myingress namespace: myns annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/healthcheck-path: /ping alb.ingress.kubernetes.io

问题 I have two AKS clusters as primary and secondary in two different regions. I want to use Azure traffic manager for the the Priority based endpoint monitoring and fail-over mechanism on the primary and secondary clusters. I got two services: A and B that routes at the relative path /service-a and /service-b respectively. I have nginx ingress controller on each cluster with PIP mapped to the custom host aks-primary.xyz.com and aks-secondary.xyz.com respectively. The services are reachable on

问题 I have a simple ingress network, I want to access services at different namespaces, from this ingress network. How I can do this? My ingress network yaml file: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: ingress spec: rules: - host: api.myhost.com http: paths: - backend: serviceName: bookapi-2 servicePort: 8080 path: /booking-service/ I've set the ExternalNames service type to the yaml file: apiVersion: v1 kind: Service metadata: name: bookapi-2 namespace: booking-namespace

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of