InsecureRegistries present not correct setting in DOCKER_OPTS

[maohsiang]

1. What kops version are you running? The command kops version, will display
this information.
1.19.1

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.
1.19.8

3. What cloud provider are you using?
aws

4. What commands did you run? What is the simplest way to reproduce this issue?
kop replace, kops create

5. What happened after the commands executed?
cat /etc/sysconfig/docker
DOCKER_OPTS=--insecure-registry=first.docker.registry, second.docker.registry

6. What did you expect to happen?
cat /etc/sysconfig/docker
DOCKER_OPTS=--insecure-registry=first.docker.registry --insecure-registry=second.docker.registry

9. Anything else do we need to know?
Docker ver: 20.10.3

apiVersion: kops/v1alpha2
kind: Cluster
metadata:
  name: {{env "FULL_NAME"}}
spec:
  docker:
    version: 20.10.3
    insecureRegistries:
    - first.docker.registry
    - second.docker.registry 
    registryMirrors:
    - http://docker.mirror

[hakman]

Hi @maohsiang. Sorry to be annoying, but kop replace, kops create is an actual way to reproduce the issue. Would you mind adding at least the docker config to the description?

[maohsiang]

Hi @maohsiang. Sorry to be annoying, but kop replace, kops create is an actual way to reproduce the issue. Would you mind adding at least the docker config to the description?

I updated the kops yaml in description.