Kops: Being able to pass docker_extra_opts to nodes

[felipejfc]

For being able to pass --insecure-registry for example

[justinsb]

You should now be able to specify InsecureRegistry, by editing your instance groups.

We can probably make this easier still, but hopefully this is a good start.

[manuelfelipe]

hey @justinsb, only insecure-registry is supported right now ? Is there a way of change the default --bip created by docker (docker0 bridge). trying to use this internally but the default 172.17.0.0 is already in use for something else in our case.

Thanks

[bsod90]

Hi @justinsb
Sorry for the stupid question, but how exactly the config should look like to add the --insecure-registry flag for all worker nodes?
Let's say I did kop edit ig --name ... nodes, what next?

[anandkumarpatel]

I also have not figured out how to add this option correctly:
here is what I tried

kind: InstanceGroup
metadata:
  creationTimestamp: 2017-03-28T04:42:10Z
  labels:
    kops.k8s.io/cluster: kubernetes.runnable-gamma.com
  name: nodes
spec:
  image: kope.io/k8s-1.5-debian-jessie-amd64-hvm-ebs-2017-01-09
  machineType: m4.large
  maxSize: 2
  minSize: 2
  docker:
    insecureRegistry: "cool.registry.com"
  role: Node
  subnets:
  - us-west-2a

However the docker portion does not save. I can edit the other values like max size and instance type and the files save correctly. I am guessing I am missing the correct path.

[lsjostro]

@anandkumarpatel you need to put in the clusterSpec.
$ kops edit cluster $NAME

....
 docker:
    insecureRegistry: registry.example.com
    logDriver: json-file
....

[kamalguptad]

@lsjostro after doing this kops is giving this message:

A copy of your changes has been stored to "/tmp/kops-edit-2gdnyyaml"

Edit cancelled, no valid changes were saved.

[JanosLiebe]

Would it be easier just to allow definition of required flags as docker_opts?
....
docker:
docker_opts=--dns 1.2.3.4 --dns 5.6.7.8 -D -l info --insecure-registry insec.reg.com --insecure-registry insec2.reg.com
....

[iBluemind]

It didn't work that insecureRegistry specified by kops edit cluster or kops edit ig if a kops cluster was already created.
I removed a kops cluster and then re-created the cluster with kops edit cluster like below when the cluster isn't created yet, then it worked.

....
 docker:
    insecureRegistry: registry.example.com
    logDriver: ""
....

[chrislovecnm]

You have to update and do a rolling update for changes to occurr.

[carlossg]

for the record, when editing using kops edit cluster you need to explicitly set logDriver or it will not validate

  docker:
    insecureRegistry: 100.64.0.0/10
    logDriver: ""

[puneethpk]

for the record, when editing using kops edit cluster you need to explicitly set logDriver or it will not validate

  docker:
    insecureRegistry: 100.64.0.0/10
    logDriver: ""

That IP which you are passing is kubedns ClusterIP right?Does it allow docker to pull images within the cluster?