kubernetes-ingress

I have a working Cluster with services that all respond behind a helm installed Ingress nGinx running on Azure AKS. This ended up being Azure specific. My question is: Why does my connection to the services / pods in this cluster periodically get severed (apparently by some sort of idle timeout), and why does that connection severing appear to also coincide with my Az AKS Browse UI connection getting cut? This is an effort to get a final answer on what exactly triggers the time-out that causes the local 'Browse' proxy UI to disconnect from my Cluster (more background on why I am asking to

Kubernetes documentation example here shows how a network policy can be applied for a source specified by either a pod selector OR a namespace selector. Can I specify a source the fulfills both constraints at the same time. e.g. Can a source be a pod with label "tier=web" which is deployed in namespace "ingress". P.S. For now, I have it working by adding namespace name as pod-labels. Yes, this is possible, but not immediately intuitive. If you look at the section below the chunk you linked, it gives a pretty good explanation (this appears to have been added after you asked your question). The

I am setting up my first ingress in kubernetes using nginx-ingress. I set up the ingress-nginx load balancer service like so: { "kind": "Service", "apiVersion": "v1", "metadata": { "name": "ingress-nginx", "namespace": "...", "labels": { "k8s-addon": "ingress-nginx.addons.k8s.io" }, "annotations": { "service.beta.kubernetes.io/aws-load-balancer-backend-protocol": "tcp", "service.beta.kubernetes.io/aws-load-balancer-proxy-protocol": "*", "service.beta.kubernetes.io/aws-load-balancer-ssl-cert": "arn....", "service.beta.kubernetes.io/aws-load-balancer-ssl-ports": "443" } }, "spec": { "ports": [ {

I understood Ingress can be used when we want to expose multiple service/routes with a single Load Balancer / public IP. Now I want to expose my Nginx server to public. I have two choices Set service type as LoadBalancer voila I got public IP Use Nginx Ingress Controller Now I can get my job done with Option 1 when or why would I choose Option 2 whats the advantage of having nginx with Ingress without Ingress ? suren There is a difference between ingress rule (ingress) and ingress controller . So, technically, nginx ingress controller and LoadBalancer type service are not comparable. You can

I am trying to wrap my brain around the suggested workarounds for the lack of built-in HTTP->HTTPS redirection in ingress-gce, using GLBC. What I am struggling with is how to use this custom backend that is suggested as one option to overcome this limitation (e.g. in How to force SSL for Kubernetes Ingress on GKE ). In my case the application behind the load-balancer does not itself have apache or nginx, and I just can't figure out how to include e.g. apache (which I know way better than nginx) in the setup. Am I supposed to set apache in front of the application as a proxy? In that case I

I'm building a service where users can build web apps - these apps will be hosted under a virtual DNS name *.laska.io For example, if Tom and Jerry both built an app, they'd have it hosted under: tom.laska.io jerry.laska.io Now, suppose I have 1000 users. Should I create one big ingress that looks like this? apiVersion: extensions/v1beta1 kind: Ingress metadata: name: nginx-ingress annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/ssl-redirect: "false" spec: rules: - host: tom.laska.io http: paths: - backend: serviceName: nginx-service servicePort: 80 - host: jerry