"cluster.spec.etcdClusters[*].version=3.1.11" --kubernetes-version 1.10.3 --cloud-labels "Team=Dev,Owner=Admin" ${NAME} You may be prompted to create a ssh public-private key pair. ssh-keygen (Please is to be installed. Please note [Kops 1.9 officially supports k8s version 1.9] --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster ${NAME} : Name of the cluster. Make sure the name ends with via 172.0.32.1 dev eth0 proto dhcp src 172.0.50.227 metric 1024 10.2.0.0/24 via 10.2.0.172 dev cilium_host src 10.2.0.172 10.2.1.0/24 via 172.0.51.175 dev eth0 proto 17 10.2.2.0/24 dev tun-172011760 proto

to be installed. Please note [Kops 1.9 officially supports k8s version 1.9] --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster ${NAME} : Name of the cluster. Make sure the name ends with via 172.0.32.1 dev eth0 proto dhcp src 172.0.50.227 metric 1024 10.2.0.0/24 via 10.2.0.172 dev cilium_host src 10.2.0.172 10.2.1.0/24 via 172.0.51.175 dev eth0 proto 17 10.2.2.0/24 dev tun-172011760 proto proto 17 src 172.0.50.227 10.2.3.0/24 dev tun-1720186231 proto 17 src 172.0.50.227 In the above example, we see three categories of routes that have been installed: Local PodCIDR: This route points to

us-west-2b,us-west-2c -- zones us-west-2a,us-west-2b,us-west-2c --networking cilium --cloud- labels "Team=Dev,Owner=Admin" ${NAME} --yes You may be prompted to create a ssh public-private key pair. ssh-keygen on the configuration options kops offers. See the kops cluster spec documentation [https://pkg.go.dev/k8s.io/kops/pkg/apis/kops? tab=doc#CiliumNetworkingSpec] for a comprehensive list of all the options which will use a dedicated etcd cluster as key/value store instead of CRDs. --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster that will be applied to your instances ${NAME} : Name of the

us-west-2b,us-west-2c -- zones us-west-2a,us-west-2b,us-west-2c --networking cilium --cloud- labels "Team=Dev,Owner=Admin" ${NAME} --yes You may be prompted to create a ssh public-private key pair. $ ssh-keygen on the configuration options kops offers. See the kops cluster spec documentation [https://pkg.go.dev/k8s.io/kops/pkg/apis/kops? tab=doc#CiliumNetworkingSpec] for a comprehensive list of all the options which will use a dedicated etcd cluster as key/value store instead of CRDs. --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster that will be applied to your instances ${NAME} : Name of the

us-west-2b,us-west-2c -- zones us-west-2a,us-west-2b,us-west-2c --networking cilium --cloud- labels "Team=Dev,Owner=Admin" ${NAME} --yes You may be prompted to create a ssh public-private key pair. $ ssh-keygen on the configuration options kops offers. See the kops cluster spec documentation [https://pkg.go.dev/k8s.io/kops/pkg/apis/kops? tab=doc#CiliumNetworkingSpec] for a comprehensive list of all the options which will use a dedicated etcd cluster as key/value store instead of CRDs. --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster that will be applied to your instances ${NAME} : Name of the

us-west-2b,us-west-2c -- zones us-west-2a,us-west-2b,us-west-2c --networking cilium --cloud- labels "Team=Dev,Owner=Admin" ${NAME} --yes You may be prompted to create a ssh public-private key pair. ssh-keygen on the configuration options kops offers. See the kops cluster spec documentation [https://pkg.go.dev/k8s.io/kops/pkg/apis/kops? tab=doc#CiliumNetworkingSpec] for a comprehensive list of all the options which will use a dedicated etcd cluster as key/value store instead of CRDs. --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster that will be applied to your instances ${NAME} : Name of the

us-west-2b,us-west-2c -- zones us-west-2a,us-west-2b,us-west-2c --networking cilium --cloud- labels "Team=Dev,Owner=Admin" ${NAME} --yes You may be prompted to create a ssh public-private key pair. ssh-keygen on the configuration options kops offers. See the kops cluster spec documentation [https://pkg.go.dev/k8s.io/kops/pkg/apis/kops? tab=doc#CiliumNetworkingSpec] for a comprehensive list of all the options which will use a dedicated etcd cluster as key/value store instead of CRDs. --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster that will be applied to your instances ${NAME} : Name of the