update Helm values once the cluster is running by changing the CiliumConfig object, e.g. with kubectl edit ciliumconfig -n cilium cilium. You may need to restart the Cilium agent pods for certain options configuring your Kubernetes cluster setup, you should consider copying the sample inventory. Then, you can edit the variables in the relevant file in the group_vars directory. $ cp -r inventory/sample inventory/my-inventory page that opens, provide a name for the cluster. Next to the Cluster Options section click the box to Edit as YAML. The configuration for the cluster will open up in an editor in the window. Remove all configuration

update Helm values once the cluster is running by changing the CiliumConfig object, e.g. with kubectl edit ciliumconfig -n cilium cilium. You may need to restart the Cilium agent pods for certain options configuring your Kubernetes cluster setup, you should consider copying the sample inventory. Then, you can edit the variables in the relevant file in the group_vars directory. $ cp -r inventory/sample inventory/my-inventory page that opens, provide a name for the cluster. Next to the Cluster Options section click the box to Edit as YAML. The configuration for the cluster will open up in an editor in the window. Remove all configuration

listed as wildcards for the kubernetes block like this: Kubernetes 1.16+ kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes forward . /etc/resolv.conf cache 30 } Kubernetes < 1.16 kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health configuring your Kubernetes cluster setup, you should consider copying the sample inventory. Then, you can edit the variables in the relevant file in the group_vars directory. $ cp -r inventory/sample inventory/my-inventory

and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health com/cilium/cilium/v1.5/examples/kubernet Open cilium-external-etcd.yaml and find the cilium-config ConfigMap and edit the endpoints: to include the list of all your etcd endpoints or a service IP that will load-balance and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health

arpa and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes page that opens, provide a name for the cluster. Next to the Cluster Options section click the box to Edit as YAML. The configuration for the cluster will open up in an editor in the window. Remove all configuration https://raw.githubusercontent.com/cilium/cilium/v1.8/inst Edit the ClusterRole for Cilium to give it access to Kubernetes secrets $ kubectl edit clusterrole cilium -n kube-system Add the following section

arpa and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes uter-only-advertise- routes.yaml Open the file generic-kuberouter-only-advertise-routes.yaml and edit the args: section. The following arguments are requried to be set to exactly these values: - --run-router=true cluster-id ConfigMap option. The value must be between 1 and 255. kubectl -n kube-system edit cm cilium-config [ ... add/edit ... ] cluster-name: cluster1 cluster-id: "1" Repeat this step for each cluster.

arpa and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns [...] apiVersion: v1 data: Corefile: | .:53 { errors health kubernetes https://raw.githubusercontent.com/cilium/cilium/v1.7/inst Edit the ClusterRole for Cilium to give it access to Kubernetes secrets $ kubectl edit clusterrole cilium -n kube-system Add the following section outer-only-advertise-routes.yaml Open the file generic-kuberouter-only-advertise-routes.yaml and edit the args: section. The following arguments are requried to be set to exactly these values: - "--run-router=true"