nginx-ingress

Kubernetes - RBAC issue with ingress controller

纵然是瞬间 提交于 2021-01-29 08:31:10
问题 I'm following a tutorial by Diego Martínez, outlining how to use an ingress controller with SSL on K8s. Everything works fine, with the exception of an RBAC error: It seems the cluster it is running with Authorization enabled (like RBAC) and there is no permissions for the ingress controller. Please check the configuration Does anyone know how I can grant RBAC permissions to this resource? I'm running on Google Cloud, and for reference, below is the ingress deployment spec 回答1: If you are

Problem configuring websphere application server behind ingress

不打扰是莪最后的温柔 提交于 2021-01-29 07:08:37
问题 I am running websphere application server deployment and service (type LoadBalancer). The websphere admin console works fine at URL https://svcloadbalancerip:9043/ibm/console/logon.jsp NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE was-svc LoadBalancer x.x.x.x x.x.x.x 9080:30810/TCP,9443:30095/TCP,9043:31902/TCP,7777:32123/TCP,31199:30225/TCP,8880:31027/TCP,9100:30936/TCP,9403:32371/TCP 2d5h But if i configure that websphere service behind ingress using ingress file like: apiVersion: networking

Getting nginx-ingress to use UDP in Azure

久未见 提交于 2021-01-29 05:14:15
问题 Currently this setup worked for TCP but once switched to UDP I get the error The Service "nginx-ingress-controller" is invalid: spec.ports: Invalid value: []core.ServicePort{core.ServicePort{Name:"proxied-udp-30001", Protocol:"UDP", Port:30001, TargetPort:intstr.IntOrString{Type:0, IntVal:30001, StrVal:""}, NodePort:0}, core.ServicePort{Name:"proxied-udp-30002", Protocol:"UDP", Port:30002, TargetPort:intstr.IntOrString{Type:0, IntVal:30002, StrVal:""}, NodePort:0}, core.ServicePort{Name:"http

How to get clients public IP on the pod?

老子叫甜甜 提交于 2021-01-28 22:08:21
问题 I have an application based on Python-Flask. I would like to get Clients Public Ip when they are hits my ingress endpoint. I have already tried to change externalTrafficPolicy to Local and Cluster. My Pod YAML file apiVersion: v1 kind: Pod metadata: labels: run: webplatform name: webplatform-deployment-6d68c99fc7-xlb8j namespace: prod spec: containers: - command: - python - /app/app.py envFrom: - secretRef: name: webplatform-secret optional: false image: docker.fuchicorp.com/webplatform-prod

How to set the ssl-session-cache values in configmap - kubernetes?

白昼怎懂夜的黑 提交于 2021-01-27 17:50:24
问题 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,

Ingress Nginx - how to serve assets to application

江枫思渺然 提交于 2021-01-25 07:08:08
问题 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.

Ingress Nginx - how to serve assets to application

本小妞迷上赌 提交于 2021-01-25 07:07:08
问题 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.

How to fix ingress 404 default backend

我的梦境 提交于 2021-01-24 07:44:12
问题 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

How to fix ingress 404 default backend

谁说胖子不能爱 提交于 2021-01-24 07:42:41
问题 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

Sticky sessions on Kubernetes cluster

霸气de小男生 提交于 2021-01-21 04:04:22
问题 Currently, I'm trying to create a Kubernetes cluster on Google Cloud with two load balancers : one for backend (in Spring boot) and another for frontend (in Angular), where each service (load balancer) communicates with 2 replicas (pods). To achieve that, I created the following ingress: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: sample-ingress spec: rules: - http: paths: - path: /rest/v1/* backend: serviceName: sample-backend servicePort: 8082 - path: /* backend: