kubernetes-ingress

问题 I'm trying to do a straight up thing that I would think is simple. I need to have https://localhost:44301, https://localhost:5002, https://localhost:5003 to be listened to in my k8s environment in docker desktop, and be proxied using a pfx file/password that I specify and have it forward by the port to pods listening on specific addresses (could be port 80, doesn't matter) The documentation is mind numbingly complex for what looks like it should be straight forward. I can get the pods running

问题 I'm trying to do a straight up thing that I would think is simple. I need to have https://localhost:44301, https://localhost:5002, https://localhost:5003 to be listened to in my k8s environment in docker desktop, and be proxied using a pfx file/password that I specify and have it forward by the port to pods listening on specific addresses (could be port 80, doesn't matter) The documentation is mind numbingly complex for what looks like it should be straight forward. I can get the pods running

问题 I have an issue at work with K8s Ingress and I will use fake examples here to illustrate my point. Assume I have an app called Tweeta and my company is called ABC. My app currently sits on tweeta.abc.com. But we want to migrate our app to app.abc.com/tweeta. My current ingress in K8s is as belows: apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: tweeta-ingress spec: rules: - host: tweeta.abc.com http: paths: - path: / backend: serviceName: tweeta-frontend servicePort: 80 -

问题 I try to set the value of the ssl-session-cache in my configmap for ingress-controller, the problem is, that i can't find how to write it correct. I need following changes in the nginx config: ssl-session-cache builtin:3000 shared:SSL:100m ssl-session-timeout: 3000 when i add ssl-session-timeout: "3000" to the config map, it works correct - this i can see in nginx-config few seconds later. but how i should write ssl-session-cache? ssl-session-cache: builtin:"3000" shared:SSL:"100m" goes well,

问题 I have an issue, I am deploying an application on [hostname]/product/console, but the .css .js files are being requested from [hostname]/product/static, hence they are not being loaded and I get 404. I have tried nginx.ingress.kubernetes.io/rewrite-target: to no avail. I also tried using: nginx.ingress.kubernetes.io/location-snippet: | location = /product/console/ { proxy_pass http://[hostname]/product/static/; } But the latter does not seem to be picked up by the nginx controller at all.

问题 I have an issue, I am deploying an application on [hostname]/product/console, but the .css .js files are being requested from [hostname]/product/static, hence they are not being loaded and I get 404. I have tried nginx.ingress.kubernetes.io/rewrite-target: to no avail. I also tried using: nginx.ingress.kubernetes.io/location-snippet: | location = /product/console/ { proxy_pass http://[hostname]/product/static/; } But the latter does not seem to be picked up by the nginx controller at all.

问题 I started to use Kubernetes few month ago and I actually migrate my microServices to my rancher cluster (RKE). Everything works good, my deployments are good and services too. I would like use ingress. Everything looks good, services are find by ingress and pods are find by services. However when I try to go to the website, I have a 404 error page from ingress controller. You can see my configuration for juste two paths : one nginx and on grafana. Someone knows how can i fix it and use

问题 I started to use Kubernetes few month ago and I actually migrate my microServices to my rancher cluster (RKE). Everything works good, my deployments are good and services too. I would like use ingress. Everything looks good, services are find by ingress and pods are find by services. However when I try to go to the website, I have a 404 error page from ingress controller. You can see my configuration for juste two paths : one nginx and on grafana. Someone knows how can i fix it and use

问题 I have added few custom cipher suites at the gateway like this : tls: mode: MUTUAL credentialName: sds minProtocolVersion: TLSV1_2 maxProtocolVersion: TLSV1_3 cipherSuites: [ECDHE-ECDSA-AES256-GCM-SHA384|ECDHE-ECDSA-AES128-GCM-SHA256|ECDHE-RSA-AES256-GCM-SHA384|ECDHE-RSA-AES128-GCM-SHA256|ECDHE-ECDSA-AES256-CBC-SHA384|ECDHE-ECDSA-AES128-CBC-SHA256|ECDHE-RSA-AES256-CBC-SHA384|ECDHE-RSA-AES128-CBC-SHA256] Is there a way to validate if these cipher suites have actually been added? Does it order

问题 I have a React app which I build and dockerize to be hosted on a nginx server. FROM nginx:latest COPY build /usr/share/nginx/html I then create a simple deployment and service for it (which I very much doubt are the problem). Next I create an nginx ingress. apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: my-app-ingress annotations: kubernetes.io/ingress.class: "nginx" nginx.ingress.kubernetes.io/ssl-redirect: "false" nginx.ingress.kubernetes.io/rewrite-target: / spec: