DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge bfaf951477 into b2ad9e7078

Browse source
This commit is contained in:
Dastan 2017-09-14 00:34:49 +00:00 committed by GitHub
commit 38715ac4e2
2 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
controllers/nginx/Makefile
View file

@ -54,7 +54,9 @@ endif
# QEMUARCH=s390x
#endif
TEMP_DIR := $(shell mktemp -d)
ifndef TEMP_DIR
TEMP_DIR := $(shell mktemp -d)
endif
DOCKERFILE := $(TEMP_DIR)/rootfs/Dockerfile

6
controllers/nginx/README.md
View file

@ -102,9 +102,10 @@ Usage of :
Before deploying the controller to production you might want to run it outside the cluster and observe it.
```console
$ make build
$ tmpdir=$(mktemp -d)
$ TEMP_DIR=${tmpdir} make build
$ mkdir /etc/nginx-ssl
$ ./rootfs/nginx-ingress-controller --running-in-cluster=false --default-backend-service=kube-system/default-http-backend
$ ${tmpdir}/rootfs/nginx-ingress-controller --running-in-cluster=false --default-backend-service=kube-system/default-http-backend
```
## Deployment
@ -115,7 +116,6 @@ $ kubectl create -f examples/default-backend.yaml
```
Follow the [example-deployment](../../examples/deployment/nginx/README.md) steps to deploy nginx-ingress-controller in Kubernetes cluster (you may prefer other type of workloads, like Daemonset, in production environment).
Loadbalancers are created via a ReplicationController or Daemonset:
## HTTP