kops/addons/ingress-nginx
Justin Santa Barbara f07eebee3f Add ingress nginx addons
We aren't wiring them into addons.yaml (not that I think anyone is using
that anyway yet), until a non-beta release is done, and likely until we
have a way to choose between AWS and GCE configurations.
2017-05-02 15:26:40 -04:00
..
README.md Simple ingress-nginx example 2016-10-05 10:44:32 -04:00
addon.yaml fix addon name 2016-10-05 12:23:11 -04:00
v1.4.0.yaml fix health-check port 2016-10-05 12:12:25 -04:00
v1.6.0-gce.yaml Add ingress nginx addons 2017-05-02 15:26:40 -04:00
v1.6.0.yaml Add ingress nginx addons 2017-05-02 15:26:40 -04:00

README.md

Creating a simple ingress

kubectl run echoheaders --image=gcr.io/google_containers/echoserver:1.4 --replicas=1 --port=8080
kubectl expose deployment echoheaders --port=80 --target-port=8080 --name=echoheaders-x
kubectl expose deployment echoheaders --port=80 --target-port=8080 --name=echoheaders-y

kubectl apply -f https://raw.githubusercontent.com/kubernetes/contrib/master/ingress/controllers/nginx/examples/ingress.yaml

kubectl get services ingress-nginx -owide

NAME            CLUSTER-IP      EXTERNAL-IP                                                               PORT(S)          AGE       SELECTOR
ingress-nginx   100.71.196.44   a29c28f4b8b0811e685cb0a924c5a8a1-1593015597.us-east-1.elb.amazonaws.com   80/TCP,443/TCP   13m       app=ingress-nginx

curl -v -H "Host: bar.baz.com" http://a29c28f4b8b0811e685cb0a924c5a8a1-1593015597.us-east-1.elb.amazonaws.com/bar