nginx-ingress

问题 This question is similar to the question but this is more around the path in the rule that can be configured. The ingress should be able to handle both the internal services and an external service. The Url for the external service should be something like http://host_name:80/es. When the user hits this url, this should be redirected to the external service. The service definition and the ingress rule are configured as below but it leads to 404. Where am i going wrong? Ingress rules

问题 I have a GKE cluster (1.12.10-gke.17). I'm running the nginx-ingress-controller with type: LoadBalancer . I've set externalTrafficPolicy: Local to preserve the source ip. Everything works great, except during rolling updates. I have maxSurge: 1 and maxUnavailable: 0 . My problem is that during a rolling update, I start getting request timeouts. I suspect the Google load balancer is still sending requests to the node where the pod is Terminating even though the health checks are failing. This

问题 Using the Nginx Ingress Controller, we would like to expose different paths of a Kubernetes service, with different security requirements. / is open to the public /white-list only allows connections from a specific IP Address /need-key requires an API key I'm running in AWS EKS. Kubernetes version is as follows: v1.12.6-eks-d69f1b . If we use Annotations, they apply to the entire service. Ideally I would like to apply an Annotation only to a path. apiVersion: extensions/v1beta1 kind: Ingress

问题 I can't connect to my app running with nginx ingress (Docker Desktop win 10). The nginx-ingress controller pod is running, the app is healthy, and I have created an ingress. However, when I try to connect to my app on localhost, I get "connection refused". I see this error in the log: [14:13:13.028][VpnKit ][Info ] vpnkit.exe: Connected Ethernet interface f6:16:36:bc:f9:c6 [14:13:13.028][VpnKit ][Info ] vpnkit.exe: UDP interface connected on 10.96.181.150 [14:13:22.320][GoBackendProcess ]

问题 I can't connect to my app running with nginx ingress (Docker Desktop win 10). The nginx-ingress controller pod is running, the app is healthy, and I have created an ingress. However, when I try to connect to my app on localhost, I get "connection refused". I see this error in the log: [14:13:13.028][VpnKit ][Info ] vpnkit.exe: Connected Ethernet interface f6:16:36:bc:f9:c6 [14:13:13.028][VpnKit ][Info ] vpnkit.exe: UDP interface connected on 10.96.181.150 [14:13:22.320][GoBackendProcess ]

问题 I am using this Ingress it is similar to Nginx: https://cloud.ibm.com/docs/containers?topic=containers-ingress_annotation#general When I do: request -> LoadBalancer Service -> client source public IP returned request -> Ingress -> LoadBalancer Service -> some private IP returned I would like to preserve the client source public IP. In my Service I am setting ExternalTrafficPolicy: Local , and it works when hitting the LoadBalancer directly, but I do not know what setting I require when going

问题 I have a backend using https. I want to separate load on that back-end based on URL/path. I decided to use ingress to do this url/path based logic in order to move traffic to different back-ends ( same back-ends , just duplicated to different NodePorts ) my question is how I can configure the ingress to receive https requests and to forward those https requests to the https back-end? thanks edit: I added the yaml file: spec: rules: - http: paths: - backend: serviceName: service servicePort:

问题 My Kubernetes cluster uses a replicaSet to run N similar pods. Each pod can only handles one websocket connection du to resource limitations. My Kubernetes uses a nginx ingress controller. Is there any way to make nginx dispatch only one incoming websocket connection per pod and in case of lack of available pods, refuses the incoming connection ? 回答1: I'm not super familiar with the Kubernetes Nginx ingress setup, but assuming it exposes some of the Nginx configuration options for setting up

问题 I am trying to host a django website on Azure kubernetes service behide nginx-ingress, and I would like my django web show under a path. e.g. when access the default admin site, I would like to access it at http://example.com/django/admin instead of http://example.com/admin I tried the configure below, when I access http://example.com/django/admin it will forward me to http://example.com/admin and show me 404 error from default ingress backend, as I set django debug to ture I assume this mean

问题 I want to set up an ingress controller on AWS EKS for several microservices that are accessed from an external system. The microservices are accessed via virtual host-names like svc1.acme.com , svc2.acme.com , ... I set up the nginx ingress controller with a helm chart: https://github.com/helm/charts/tree/master/stable/nginx-ingress My idea was to reserve an Elastic IP Address and bind the nginx-controller to that IP by setting the variable externalIP. This way I should be able to access the