kubernetes-ingress

问题 I have a setup Metallb as LB with Nginx Ingress installed on K8S cluster. I have read about session affinity and its significance but so far I do not have a clear picture. How can I create a single service exposing multiple pods of the same application? After creating the single service entry point, how to map the specific client IP to Pod abstracted by the service? Is there any blog explaining this concept in terms of how the mapping between Client IP and POD is done in kubernetes? But I do

问题 Being new to Kubernetes, I am trying to make a simple .NET Core 3 MVC app run on Kubernetes and reply on port 443 as well as port 80. I have a working Docker-Compose setup which I am trying to port to Kubernetes. Running Docker Desktop CE with nginx-ingress on Win 10 Pro. So far it is working on port 80. (http://mymvc.local on host Win 10 - hosts file redirects mymvc.local to 127.0.0.1) My MVC app is running behind service mvc on port 5000. I've made a self-signed certificate for the domain

问题 Being new to Kubernetes, I am trying to make a simple .NET Core 3 MVC app run on Kubernetes and reply on port 443 as well as port 80. I have a working Docker-Compose setup which I am trying to port to Kubernetes. Running Docker Desktop CE with nginx-ingress on Win 10 Pro. So far it is working on port 80. (http://mymvc.local on host Win 10 - hosts file redirects mymvc.local to 127.0.0.1) My MVC app is running behind service mvc on port 5000. I've made a self-signed certificate for the domain

问题 I don't mean being able to route to a specific port, I mean to actually change the port the ingress listens on. Is this possible? How? Where is this documented? 回答1: From the kubernetes documentation: An Ingress does not expose arbitrary ports or protocols. Exposing services other than HTTP and HTTPS to the internet typically uses a service of type Service.Type=NodePort or Service.Type=LoadBalancer. It may be possible to customize a LoadBalancer on a cloud provider like AWS to listen on other

问题 I am working on spring cloud dataflow stream app. I am able to run Spring cloud data flow server with the skipper running in Cloud Foundry . Now i am trying to run the same with the skipper running in kubernetes cluster and getting below error on deployment even though i am explicitly giving the username in the environment config in deployment. Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: kubernetes_cluster_url:6443/api/v1/namespaces/pocdev

问题 I have deployed eight services on Kubernetes with Istio sidecar injection. I want to set-up routing rules in VirtualService where three services have same rule. Rules:- - match: - headers: location: exact: pune uri: prefix: /wagholi route: - destination: host: wagholi port: number: 8080 uri: prefix: /yerwada route: - destination: host: yerwada port: number: 8080 uri: prefix: /hadapsar route: - destination: host: hadapsar port: number: 8080 - match: - headers: location: exact: mumbai uri:

问题 Using ingress-nginx v0.30 in the GKE cluster has no issue creating the ingress using kubectl apply -f command. After upgrading to ingress-nginx v0.31.1 , the following error has been shown: Error from server (Timeout): error when creating "kubernetes/ingress.yaml": Timeout: request did not complete within requested timeout 30s Questions: How to debug the timeout of this request? There is no connection issue same ingress file works on v0.30 Stackdriver shows no clue Any way to increase the

问题 I have this ingress configuration but all html and json reponse pages dont contain the added header: apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: {{ $app }}-ingress labels: app: {{ $app }} chart: chart-{{ $app }} app.kubernetes.io/managed-by: Helm annotations: meta.helm.sh/release-name: {{ $app }} meta.helm.sh/release-namespace: {{ .Release.Namespace }} kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/proxy-body-size: "{{ $proxy_body_size }}" nginx.ingress

问题 I want up upgrade all incoming http 1.1 connections to http2 in Istio. I understand how to achieve this via destination rules for a particular namespace and pod. However, I want to upgrade all connections in service mesh from http1.1 too http2. Even the documentation recommends this, if Istio sidecar is auto injected here. if sidecar is installed on all pods in the mesh, then this should be set to UPGRADE. Can I update the "istio" ConfigMap under "Istio-system" namespace? If yes, what would

问题 I want up upgrade all incoming http 1.1 connections to http2 in Istio. I understand how to achieve this via destination rules for a particular namespace and pod. However, I want to upgrade all connections in service mesh from http1.1 too http2. Even the documentation recommends this, if Istio sidecar is auto injected here. if sidecar is installed on all pods in the mesh, then this should be set to UPGRADE. Can I update the "istio" ConfigMap under "Istio-system" namespace? If yes, what would