kubernetes-ingress

问题 I want to sent traffic from one port through kubernetes cluster (using minikube) to another physical port. I don't know how to route traffic from physical port to cluster and from cluster to the second physical port. I'm exposing cluster via ingress (and I tested service solution also), i have one service to send external tarffic to pod and another to sent traffic from first pod to second pod. But I really don't know how to send this traffic from port to cluster and how to sent from cluster

问题 I want to sent traffic from one port through kubernetes cluster (using minikube) to another physical port. I don't know how to route traffic from physical port to cluster and from cluster to the second physical port. I'm exposing cluster via ingress (and I tested service solution also), i have one service to send external tarffic to pod and another to sent traffic from first pod to second pod. But I really don't know how to send this traffic from port to cluster and how to sent from cluster

问题 Kubernetes has both Ingress (in front of a Service) and Service with type: LoadBalancer. These seem to do identical things: allow public traffic into the pods matching the service's selector. What are the benefits and drawbacks of each? In what scenarios would I choose one over the other? 回答1: Assume that AWS, GCP or Azure is where your infrastructure located Ingress: Only work if you have ingress controller such as nginx-ingress-controller, traefik,... Many services could share the same

问题 Kubernetes has both Ingress (in front of a Service) and Service with type: LoadBalancer. These seem to do identical things: allow public traffic into the pods matching the service's selector. What are the benefits and drawbacks of each? In what scenarios would I choose one over the other? 回答1: Assume that AWS, GCP or Azure is where your infrastructure located Ingress: Only work if you have ingress controller such as nginx-ingress-controller, traefik,... Many services could share the same

问题 I have configured ssl certificate, if I visit https://<domain>.com , I see that my certificate is configured successfully but when I try to check certificate by following command openssl s_client -connect <domain>.com:443 | openssl x509 -noout -subject -issuer i am getting Kubernetes Ingress Controller Fake Certificate My ingres config is : annotations: nginx.ingress.kubernetes.io/ssl-redirect: 'true' nginx.ingress.kubernetes.io/from-to-www-redirect: 'true' name: nginx-echo spec: tls: - hosts

问题 I have configured ssl certificate, if I visit https://<domain>.com , I see that my certificate is configured successfully but when I try to check certificate by following command openssl s_client -connect <domain>.com:443 | openssl x509 -noout -subject -issuer i am getting Kubernetes Ingress Controller Fake Certificate My ingres config is : annotations: nginx.ingress.kubernetes.io/ssl-redirect: 'true' nginx.ingress.kubernetes.io/from-to-www-redirect: 'true' name: nginx-echo spec: tls: - hosts

问题 Here is my use case: We have a customer, where each of their services has to be available on dedicated subdomain. Naming convention should be service-name.customerdomain.com , where service-name is the deployed service and customerdomain.com is the customer domain. When a new service is created, it should be available automatically , i.e. once service-name service is deployed into the cluster, it has to be available on service-name.customerdomain.com . I know, this can be achieved manually by

问题 In my kubernetes cluster I would like to do monitoring so I installed grafana. I would like to access the grafana dashboard as http://example.com/monitoring , so I tried to include this in my ingress configuration apiVersion: extensions/v1beta1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: example.com http: paths: - path: /monitoring/(.*) backend: serviceName: grafana servicePort: 80 The idea is to add other

问题 When the Ingress Nginx controller reach its full capacity does it auto scale? Is Kubernetes Ingress even scalable? 回答1: In principle, the NGINX ingress controller is indeed scalable -- it pulls its entire configuration from the Kubernetes API server and is in itself basically stateless. In practice, this depends very much on how your ingress controller is set up. First of all, the ingress controller will not auto-scale by itself. If you have deployed it using a Deployment controller, you can

问题 I have deployed few services in kubernetes and using NGINX ingress to access outside.(Using EC2 instance for all cluster setup). Able to access service through host tied with ingress. Now instead of accessing the svc directly I am trying to add authentication and before accessing the service. And redirecting to login page , user enters credentials and should redirect to the asked page. The following code snipet I I tried so far. Please guide to find solution. my-ingress.yml apiVersion: