K
Q

kubernetes v1.1 baremetal => how to connect ingress to outside world

11/21/2015

I have a setup of kubernetes on a coreos baremetal. For now I did the connection from outside world to service with a nginx reverse-proxy.

I'm trying the new Ingress resource. for now I have added a simple ingress:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: kube-ui
spec:
  backend:
    serviceName: kube-ui
    servicePort: 80

that starts like this:

INGRESS
NAME      RULE      BACKEND      ADDRESS
kube-ui   -         kube-ui:80

My question is how to connect from the outside internet to that ingress point as this resource have no ADDRESS ... ?

-- Thibault Deheurles
kubernetes

Similar Questions

Openshift V3: Confusion on Services and Routes
GKE v1.1.1 KubernetesSeedProvider NullPointerException
GKE 1.1.1 and kubectl delete resource Terminating
Upgrading GKE Kubernetes node version to v1.1.1, master still at v1.0.7 despite conflicting release notes

2 Answers

7/30/2019

check this gist

This is for the ingress-nginx, not kubernetes-ingress

  1. Pre-requirement
    kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml
  1. Exposing hostNetwork (hope you know what you are doing. As documented, other than this, you can use nodePort or loadbalancer.)
    kubectl edit deployment.apps/nginx-ingress-controller -n ingress-nginx

add

template:
  spec:
    hostNetwork: true
  1. port forwarding
   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: tcp-services
     namespace: ingress-nginx
   data:
     9000: "default/example-go:8080"
  1. Also, you can use ingress object to expose the service
-- Franci
Source: StackOverflow
11/23/2015

POSTing this to the API server will have no effect if you have not configured an Ingress controller. You need to choose the ingress controller implementation that is the best fit for your cluster, or implement one. Examples and instructions can be found here.

-- George
Source: StackOverflow