kubernetes-ingress

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. Can I try some other way to route the traffic from the internet to pod? I had the same issue and it was

I'm running through what looks like a configuration issue! I am using traefik as ingress controller within kubernetes and I have an ingress to route some URLs to route some frontends to various backends. Let's say I have something like this: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: test annotations: kubernetes.io/ingress.class: traefik traefik.frontend.rule.type: ReplacePathRegex spec: rules: - host: foo.io http: paths: - path: /api/authservice/(.*) /$1 backend: serviceName: auth servicePort: 8901 - path: /api/svcXXX/v1/files/cover/(.*) /v1/files/cover/$1 backend:

I have a kubernetes cluster, where I have deployed an nginx ingress controller using the helm nginx-ingress chart . I need to add some custom config to the nginx.conf file that is generated in the nginx-controller-pod, and I am seeing an issue where if I add a one line option such as proxy-buffer-size: "512k" I can see this reflected in the nginx.conf file and everything works as expected. However, if I attempt to add a snippet to accomplish the same thing: location-snippet: | proxy_buffer_size "512k"; It is as though this is ignored by the nginx.conf file and the proxy_buffer_size setting

I want to clear cache in all the pods in my Kubernetes namespace. I want to send one request to the end-point which will then send a HTTP call to all the pods in the namespace to clear cache. Currently, I can hit only one pod using Kubernetes and I do not have control over which pod would get hit. Even though the load-balancer is set to RR, continuously hitting the pods(n number of times, where n is the total number of pods) doesn't help as some other requests can creep in. The same issue was discussed here, but I couldn't find a solution for the implementation: https://github.com/kubernetes

I'm setting up a k8s cluster on GKE. A wildcard DNS *.server.com will point to a Ingress controller. Internally to the cluster, there will be webserver pods, each exposing a unique service. The Ingress controller will use the server name to route to the various services. Servers will be created and destroyed on a nearly daily basis. I'd like to know if there's a way to add and remove a named server from the ingress controller without editing the whole list of named servers. It appears like you're planning to host multiple domain names on a single Load Balancer (==single Ingress resource). If