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

Improve documentation format

Browse source
This commit is contained in:
Francisco de Brito Fontes 2018-04-29 03:17:29 -03:00
parent 69fce01325
commit 2f6f9a29ba
15 changed files with 163 additions and 146 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/examples/docker-registry/README.md
View file

@ -10,9 +10,10 @@ First we deploy the docker registry in the cluster:
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/docs/examples/docker-registry/deployment.yaml
```
**Important:** DO NOT RUN THIS IN PRODUCTION.
This deployment uses `emptyDir` in the `volumeMount` which means the contents of the registry will be deleted when the pod dies.
!!! Important
**DO NOT RUN THIS IN PRODUCTION**
This deployment uses `emptyDir` in the `volumeMount` which means the contents of the registry will be deleted when the pod dies.
The next required step is creation of the ingress rules. To do this we have two options: with and without TLS
@ -24,8 +25,10 @@ Download and edit the yaml deployment replacing `registry.<your domain>` with a
wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/docs/examples/docker-registry/ingress-without-tls.yaml
```
**Important:** running a docker registry without TLS requires we configure our local docker daemon with the insecure registry flag.
Please check [deploy a plain http registry](https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry)
!!! Important
Running a docker registry without TLS requires we configure our local docker daemon with the insecure registry flag.
Please check [deploy a plain http registry](https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry)
### With TLS