kubernetes-ingress

问题 I'm having difficulties getting my Ingress controller running on Google Container Engine. I want to use an NGINX Ingress Controller with Basic Auth and use a reserved global static ip name (this can be made in the External IP addresses section in the Google Cloud Admin interface). When I use the gce class everything works fine except for the Basic Auth (which I think is not supported on the gce class), anenter code hered when I try to use the nginx class the Ingress Controller launches but

问题 I am hosting my application on GKE. The kubectl version installed in the server is v1.10.11-gke.1 and nginx-ingress is nginx-ingress-0.28.2 I would like to see the client IP address in my logs. For now, I can only see the pod IP address for example: 2019-02-14 15:17:21.000 EAT 10.60.1.1 - [10.60.1.1] - - [14/Feb/2019:12:17:21 +0000] "GET /user HTTP/2.0" 404 9 "-" "Mozilla/5.0 (Macintosh; My service has tls managed by letsencrypt. How can I get the client IP address on the logs? screenshot of

问题 I have a working Cluster with services that all respond behind a helm installed Ingress nGinx running on Azure AKS. This ended up being Azure specific. My question is: Why does my connection to the services / pods in this cluster periodically get severed (apparently by some sort of idle timeout), and why does that connection severing appear to also coincide with my Az AKS Browse UI connection getting cut? This is an effort to get a final answer on what exactly triggers the time-out that

问题 I have a working Cluster with services that all respond behind a helm installed Ingress nGinx running on Azure AKS. This ended up being Azure specific. My question is: Why does my connection to the services / pods in this cluster periodically get severed (apparently by some sort of idle timeout), and why does that connection severing appear to also coincide with my Az AKS Browse UI connection getting cut? This is an effort to get a final answer on what exactly triggers the time-out that

问题 I have a virtual machine centos(ver 7.4) on win10 machine, I do not use AWS, Google cloud service, nor Azure. I put master and node in one machine. My original problem domain have 5 components, I configure them as ClusterIP, so they could communicate with each other(eureka, config,api,uaa,zipkin). Now I only need api talk outside. But for short, I make two components for convenience (api and eureka). But now, api needs to receive from outside of cluster. So that I configure ingress. When

问题 Unable to install ingress-nginx for kubernetes on Docker desktop I was using the following in cmd line to install ingress nginx so far: $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml as shown in the web page: https://che.eclipse.org/running-eclipse-che-on-kubernetes-using-docker-desktop-for-mac-5d972ed511e1 I seems

问题 I've got the following: ingress.yaml apiVersion: extensions/v1beta1 kind: Ingress metadata: name: abcxyz annotations: kubernetes.io/ingress.class: nginx spec: rules: - host: abcxyz http: paths: - path: /a/ backend: serviceName: service-a servicePort: 80 - path: /b/ backend: serviceName: service-b servicePort: 80 Output of kubectl describe ingress abcxyz : Name: abcxyz Namespace: default Address: Default backend: default-http-backend:80 (<none>) Rules: Host Path Backends ---- ---- --------

问题 I have setup Custom Nginx ingress controller with Ingress resource in Kubernetes and instead of "default-http-backend service", I used custom application as the default backend service to be served for default requests. I have also used custom SSL which is set as kubernetes secret, for my service. The issue is that when I request the hostnames which are mentioned in the rules, the https redirection works. But when the requests other than the hosts mentioned in the rules are made, it serves

问题 Given: a simple pod running an nginx a nodeport service an ingress When calling the pod from within the cluster we get a 200 response code When calling the service from within the cluster we get a 200 response code The ingress shows as annotation: ingress.kubernetes.io/backends: '{"k8s-be-30606--559b9972f521fd4f":"UNHEALTHY"}' To top things of, we have a different kubernetes cluster with the exact same configuration (apart from the namespace dev vs qa & timestamps & assigned ips & ports)

问题 This question is relevant to another question. From this link, I could say using ingress to route to different ports service is feasible. I first listed two of my services: (eureka and config), the ingress_nginx_res.yaml is as belows: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: my-ingress spec: rules: - host: http: paths: - backend: serviceName: gearbox-rack-eureka-server servicePort: 8761 - host: http: paths: - path: backend: serviceName: gearbox-rack-config-server