How to set KUBE_ENABLE_INSECURE_REGISTRY=true on a running Kubernetes cluster?

7/20/2016

I forgot to set export KUBE_ENABLE_INSECURE_REGISTRY=true when running kube-up.sh (AWS provider). I was wondering if there was anyway to retroactively apply that change to a running cluster. It is only a 3 node cluster so doing it manually is an option. Or is the only way to tear down the cluster and start from scratch?

-- Olivier Lalonde
kubernetes

1 Answer

7/20/2016

I haven't tested it but in theory you just need to add --insecure-registry 10.0.0.0/8 (if you are running your insecure registry in the kube network 10.0.0.0/8) to the docker daemon options (DOCKER_OPTS).

You can also specify the url instead of the network.

-- Javier Segura
Source: StackOverflow