kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

document --insecure-registry flag

pull/1047/head
Matthew Fisher 2017-01-26 13:33:08 -08:00
parent 075e342464
commit 63bd5d859b
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -150,6 +150,15 @@ The fix is to update /etc/sysconfig/docker to ensure that minikube's environment
Remember to turn off the imagePullPolicy:Always, as otherwise kubernetes won't use images you built locally.
#### Enabling Docker Insecure Registry
Minikube allows users to configure the docker engine's `--insecure-registry` flag. You can use the `--insecure-registry` flag on the
`minikube start` command to enable insecure communication between the docker engine and registries listening to reqeusts from the CIDR range.
One nifty hack is to allow the kubelet running in minikube to talk to registries deployed inside a pod in the cluster without backing them
with TLS certificates. Because the default service cluster IP is known to be available at 10.0.0.1, users can pull images from registries
deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`.
## Managing your Cluster
### Starting a Cluster