kubernetes-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 with getting the install packages). Intention is to be able to use kubectl on client host with

(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 the Cluster? I convert 2 certificates to 2 .key and 2 .crt files I use those files to make 2 TLS secrets

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: Always args: ["/hello-abc"] ports: - containerPort: 5000 --- apiVersion: extensions/v1beta1 kind:

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 GalloCedrone 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 can pick one by specifying the ingress.class annotation, eg creating an Ingress with an

I have an ingress-nginx controller handling traffic to my Kubernetes cluster hosted on GKE. I set it up using helm installation instructions from docs: Docs here For the most part everything is working, but if I try to set cache related parameters via a server-snippet annotation, all of the served content that should get the cache-control headers comes back as a 404 . Here's my ingress-service.yaml file: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: ingress-service annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/proxy-read-timeout: "4000" nginx

I am trying to setup ingress load balancer. Basically, I have a single backend service with multiple paths. Let's say my backend NodePort service name is hello-app. The pod associated with this service exposes multiple paths like /foo and /bar. Below is the example NodePort service and associated deployment apiVersion: v1 kind: Service metadata: name: hello-app spec: selector: app: hello-app type: NodePort ports: - protocol: "TCP" port: 7799 targetPort: 7799 --- apiVersion: apps/v1 kind: Deployment metadata: name: hello-app labels: app: hello-app spec: replicas: 1 selector: matchLabels: app: