kubernetes-ingress

问题 I need to allow requests from multiple origins: http://localhost:4200 , http://localhost:4242 , etc., on nginx-ingress version 1.7.1. But I'm not able to do that for multiple origins, because nginx.ingress.kubernetes.io/cors-allow-credentials: true will not work with nginx.ingress.kubernetes.io/cors-allow-origin: "*" . It causes the browser to generate CORS error. Maybe someone has a solution for avoiding this error? this is my config annotations: kubernetes.io/ingress.class: "nginx" nginx

问题 (While learning Kubernetes I never really found any good resources explaining this) Scenario: I own mywebsite1.com and mywebsite2.com and I want to host them both inside a Kubernetes Cluster. I deploy a generic cloud ingress controller according to the following website with 2 kubectl apply -f < url > commands. (mandatory.yaml and generic ingress.yaml) https://kubernetes.github.io/ingress-nginx/deploy/ So the question is what does that architecture look like? and how does the data flow into

问题 I am running EKS in private subnet and thus unable to create an internet facing load balancer but was able to create Internal LoadBalancer. Is there any way I can create Loadbalancer(probably Manually) in public subnet and point to the pods running in EKS in the private subnet. I was thinking of creating the chain of load balancer in which External load balancer will point to internal load balancer but that too is not possible as the IP address of the internal load balancer is reserved IP.

问题 I am running Kubernetes on "Docker Desktop" in Windows. I have a LoadBalancer Service for a deployment which has 3 replicas. I would like to access SPECIFIC pod through some means (such as via URL path : < serviceIP >:8090/pod1) . Is there any way to achieve this usecase? deployment.yaml : apiVersion: v1 kind: Service metadata: name: my-service1 labels: app: stream spec: ports: - port: 8090 targetPort: 8090 name: port8090 selector: app: stream # clusterIP: None type: LoadBalancer ---

问题 Hy We're trying to get our website working on kubernetes (running in a container using nginx). We use ingress to route to the site, here is our configuration: nginx-conf: server { listen 80; location / { root /usr/share/nginx/html; index index.html index.htm; try_files $uri $uri/ /index.html =404; } } Kubernetes deployment: apiVersion: apps/v1beta1 kind: Deployment metadata: name: mywebsite spec: replicas: 2 template: metadata: labels: app: mywebsite spec: containers: - name: mywebsite image:

问题 Kind Note: I have googled a lot and take a look too many questions related to this issue at StackOverflow also but couldn't solve my issue, that's why don't mark this as duplicate, please! I'm trying to deploy 2 services (One is Python flask and other is NodeJS) on Google Kubernetes Engine. I have created two Kubernetes-deployments one for each service and two Kubernetes-services one for each service of type NodePort . Then, I have created an Ingress and mentioned my endpoints but Ingress

问题 I was trying unsuccessfully access Kubernetes API via HTTPS ingress and now started to wonder if that is possible at all? Any working detailed guide for a direct remote access (without using ssh -> kubectl proxy to avoid user management on Kubernetes node) would be appreciated. :) UPDATE: Just to make more clear. This is bare metal on premise deployment (NO GCE, AWZ, Azure or any other) and there is intension that some environments will be totally offline (which will add additional issues

问题 I've configured my Kubernetes to use one wildcard SSL certificate to all my apps using cert-manager and letsencrypt, now the problem is that I can't configure subdomain redirects cause Ingress is kinda "stiff". Here's how I'm trying to achieve this: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: my-wildcard-ingress namespace: mynamespace annotations: kubernetes.io/ingress.class: nginx certmanager.k8s.io/cluster-issuer: letsencrypt-prod certmanager.k8s.io/acme-challenge-type:

问题 I have the following pods hello-abc and hello-def . And I want to send data from hello-abc to hello-def . How would pod hello-abc know the IP address of hello-def ? And I want to do this programmatically. What's the easiest way for hello-abc to find where hello-def ? --- apiVersion: extensions/v1beta1 kind: Deployment metadata: name: hello-abc-deployment spec: replicas: 1 template: metadata: labels: app: hello-abc spec: containers: - name: hello-abc image: hello-abc:v0.0.1 imagePullPolicy:

问题 I have been using the Google Cloud ingress. Also deployed the nginx-ingress and trying to setup using static-ip address in GKE. Can we use both Google Cloud ingress and nginx-ingress in same cluster? How can we use the nginx-ingress with static-ip? Thanks 回答1: First question As Radek 'Goblin' Pieczonka already pointed you out it is possible to do so. I just wanted to link you to the official documentation regarding this matter: If you have multiple Ingress controllers in a single cluster, you