Helm Reference

The table below serves as a reference for the values that can be set on Cilium’s Helm chart.

KeyDescriptionTypeDefault
affinityPod affinity for cilium-agent.object{“podAntiAffinity”:{“requiredDuringSchedulingIgnoredDuringExecution”:[{“labelSelector”:{“matchExpressions”:[{“key”:”k8s-app”,”operator”:”In”,”values”:[“cilium”]}]},”topologyKey”:”kubernetes.io/hostname”}]}}
agentInstall the cilium agent resources.booltrue
autoDirectNodeRoutesEnable installation of PodCIDR routes between worker nodes if worker nodes share a common L2 network segment.boolfalse
azure.enabledEnable Azure integrationboolfalse
bandwidthManagerOptimize TCP and UDP workloads and enable rate-limiting traffic from individual Pods with EDT (Earliest Departure Time) through the “kubernetes.io/egress-bandwidth” Pod annotation.boolfalse
bpf.clockProbeEnable BPF clock source probing for more efficient tick retrieval.boolfalse
bpf.lbMapMaxConfigure the maximum number of service entries in the load balancer maps.int65536
bpf.monitorAggregationConfigure the level of aggregation for monitor notifications. Valid options are none, low, medium, maximum.string“medium”
bpf.monitorFlagsConfigure which TCP flags trigger notifications when seen for the first time in a connection.string“all”
bpf.monitorIntervalConfigure the typical time between monitor notifications for active connections.string“5s”
bpf.policyMapMaxConfigure the maximum number of entries in endpoint policy map (per endpoint).int16384
bpf.preallocateMapsEnables pre-allocation of eBPF map values. This increases memory usage but can reduce latency.boolfalse
bpf.waitForMountForce the cilium-agent DaemonSet to wait in an initContainer until the eBPF filesystem has been mounted.boolfalse
certgenConfigure certificate generation for Hubble integration. If hubble.tls.auto.method=cronJob, these values are used for the Kubernetes CronJob which will be scheduled regularly to (re)generate any certificates not provided manually.object{“image”:{“pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/certgen”,”tag”:”v0.1.3”},”podLabels”:{},”ttlSecondsAfterFinished”:1800}
certgen.podLabelsLabels to be added to hubble-certgen podsobject{}
certgen.ttlSecondsAfterFinishedSeconds after which the completed job pod will be deletedint1800
cleanBpfStateClean all eBPF datapath state from the initContainer of the cilium-agent DaemonSet. WARNING: Use with care!boolfalse
cleanStateClean all local Cilium state from the initContainer of the cilium-agent DaemonSet. Implies cleanBpfState: true. WARNING: Use with care!boolfalse
cluster.idUnique ID of the cluster. Must be unique across all connected clusters and in the range of 1 to 255. Only required for Cluster Mesh.intnil
cluster.nameName of the cluster. Only required for Cluster Mesh.string“default”
clustermesh.apiserver.etcd.imageClustermesh API server etcd image.object{“pullPolicy”:”IfNotPresent”,”repository”:”quay.io/coreos/etcd”,”tag”:”v3.4.13”}
clustermesh.apiserver.imageClustermesh API server image.object{“digest”:”sha256:c56dfe3d1c6cbb75dd6fe1a2ee9f4156bfc8da34586cec61cf590226ea0e2f23”,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/clustermesh-apiserver”,”tag”:”v1.9.8”,”useDigest”:false}
clustermesh.apiserver.nodeSelectorNode labels for pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
clustermesh.apiserver.podAnnotationsAnnotations to be added to clustermesh-apiserver podsobject{}
clustermesh.apiserver.podLabelsLabels to be added to clustermesh-apiserver podsobject{}
clustermesh.apiserver.replicasNumber of replicas run for the clustermesh-apiserver deployment.int1
clustermesh.apiserver.resourcesResource requests and limits for the clustermesh-apiserver container of the clustermesh-apiserver deployment, such as resources: limits: cpu: 1000m memory: 1024M requests: cpu: 100m memory: 64Miobject{}
clustermesh.apiserver.service.annotationsAnnotations for the clustermesh-apiserver For GKE LoadBalancer, use annotation cloud.google.com/load-balancer-type: “Internal” For EKS LoadBalancer, use annotation service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0object{}
clustermesh.apiserver.service.nodePortOptional port to use as the node port for apiserver access.int32379
clustermesh.apiserver.service.typeThe type of service used for apiserver access.string“NodePort”
clustermesh.apiserver.tls.adminbase64 encoded PEM values for the clustermesh-apiserver admin certificate and private key. Used if ‘auto’ is not enabled.object{“cert”:””,”key”:””}
clustermesh.apiserver.tls.autoConfigure automatic TLS certificates generation. A Kubernetes CronJob is used the generate any certificates not provided by the user at installation time.object{“certValidityDuration”:1095,”enabled”:true,”method”:”helm”}
clustermesh.apiserver.tls.auto.certValidityDurationGenerated certificates validity duration in days.int1095
clustermesh.apiserver.tls.auto.enabledWhen set to true, automatically generate a CA and certificates to enable mTLS between clustermesh-apiserver and external workload instances. If set to false, the certs to be provided by setting appropriate values below.booltrue
clustermesh.apiserver.tls.cabase64 encoded PEM values for the ExternalWorkload CA certificate and private key.object{“cert”:””,”key”:””}
clustermesh.apiserver.tls.ca.certOptional CA cert. If it is provided, it will be used by the ‘cronJob’ method to generate all other certificates. Otherwise, an ephemeral CA is generated.string“”
clustermesh.apiserver.tls.ca.keyOptional CA private key. If it is provided, it will be used by the ‘cronJob’ method to generate all other certificates. Otherwise, an ephemeral CA is generated.string“”
clustermesh.apiserver.tls.clientbase64 encoded PEM values for the clustermesh-apiserver client certificate and private key. Used if ‘auto’ is not enabled.object{“cert”:””,”key”:””}
clustermesh.apiserver.tls.remotebase64 encoded PEM values for the clustermesh-apiserver remote cluster certificate and private key. Used if ‘auto’ is not enabled.object{“cert”:””,”key”:””}
clustermesh.apiserver.tls.serverbase64 encoded PEM values for the clustermesh-apiserver server certificate and private key. Used if ‘auto’ is not enabled.object{“cert”:””,”key”:””}
clustermesh.apiserver.tolerationsNode tolerations for pod assignment on nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[]
clustermesh.apiserver.updateStrategyclustermesh-apiserver update strategyobject{“rollingUpdate”:{“maxUnavailable”:1},”type”:”RollingUpdate”}
clustermesh.useAPIServerDeploy clustermesh-apiserver for clustermeshboolfalse
cni.binPathConfigure the path to the CNI binary directory on the host.string“/opt/cni/bin”
cni.chainingModeConfigure chaining on top of other CNI plugins. Possible values: - none - generic-veth - aws-cni - portmapstring“none”
cni.confFileMountPathConfigure the path to where to mount the ConfigMap inside the agent pod.string“/tmp/cni-configuration”
cni.confPathConfigure the path to the CNI configuration directory on the host.string“/etc/cni/net.d”
cni.configMapKeyConfigure the key in the CNI ConfigMap to read the contents of the CNI configuration from.string“cni-config”
cni.customConfSkip writing of the CNI configuration. This can be used if writing of the CNI configuration is performed by external automation.boolfalse
cni.hostConfDirMountPathConfigure the path to where the CNI configuration directory is mounted inside the agent pod.string“/host/etc/cni/net.d”
cni.installInstall the CNI configuration and binary files into the filesystem.booltrue
containerRuntimeConfigure container runtime specific integration.object{“integration”:”none”}
containerRuntime.integrationEnables specific integrations for container runtimes. Supported values: - containerd - crio - docker - none - auto (automatically detect the container runtime)string“none”
daemon.runPathConfigure where Cilium runtime state should be stored.string“/var/run/cilium”
datapathModeConfigure which datapath mode should be used for configuring container connectivity. Valid options are “veth” or “ipvlan”.string“veth”
debug.enabledEnable debug loggingboolfalse
enableCnpStatusUpdatesWhether to enable CNP status updates.boolfalse
enableCriticalPriorityClassExplicitly enable or disable priority class. .Capabilities.KubeVersion is unsettable in helm template calls, it depends on k8s libraries version that Helm was compiled against. This option allows to explicitly disable setting the priority class, which is useful for rendering charts for gke clusters in advance.booltrue
enableXTSocketFallbackEnables the fallback compatibility solution for when the xt_socket kernel module is missing and it is needed for the datapath L7 redirection to work properly. See documentation for details on when this can be disabled: http://docs.cilium.io/en/stable/install/system_requirements/#admin-kernel-version.booltrue
encryption.enabledEnable transparent network encryption.boolfalse
encryption.keyFileName of the key file inside the Kubernetes secret configured via secretName.string“keys”
encryption.mountPathPath to mount the secret inside the Cilium pod.string“/etc/ipsec”
encryption.nodeEncryptionEnable encryption for pure node to node traffic.boolfalse
encryption.secretNameName of the Kubernetes secret containing the encryption keys.string“cilium-ipsec-keys”
endpointHealthChecking.enabledEnable connectivity health checking between virtual endpoints.booltrue
endpointRoutes.enabledEnable use of per endpoint routes instead of routing via the cilium_host interface.boolfalse
eniEnable Elastic Network Interface (ENI) integration.boolfalse
etcd.clusterDomainCluster domain for cilium-etcd-operator.string“cluster.local”
etcd.clusterSizeSize of the managed etcd cluster.int3
etcd.enabledEnable etcd mode for the agent.boolfalse
etcd.endpointsList of etcd endpoints (not needed when using managed=true).list[“https://CHANGE-ME:2379“]
etcd.extraArgsAdditional cilium-etcd-operator container arguments.object{}
etcd.extraConfigmapMountsAdditional cilium-etcd-operator ConfigMap mounts.list[]
etcd.extraHostPathMountsAdditional cilium-etcd-operator hostPath mounts.list[]
etcd.extraInitContainersAdditional InitContainers to initialize the pod.list[]
etcd.imagecilium-etcd-operator image.object{“pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/cilium-etcd-operator”,”tag”:”v2.0.7”}
etcd.k8sServiceIf etcd is behind a k8s service set this option to true so that Cilium does the service translation automatically without requiring a DNS to be running.boolfalse
etcd.managedEnable managed etcd mode based on the cilium-etcd-operator.boolfalse
etcd.nodeSelectorNode labels for cilium-etcd-operator pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
etcd.podAnnotationsAnnotations to be added to cilium-etcd-operator podsobject{}
etcd.podDisruptionBudgetPodDisruptionBudget settings ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/object{“enabled”:true,”maxUnavailable”:2}
etcd.podLabelsLabels to be added to cilium-etcd-operator podsobject{}
etcd.priorityClassNamecilium-etcd-operator priorityClassNamestring“”
etcd.resourcescilium-etcd-operator resource limits & requests ref: https://kubernetes.io/docs/user-guide/compute-resources/object{}
etcd.securityContextSecurity context to be added to cilium-etcd-operator podsobject{}
etcd.sslEnable use of TLS/SSL for connectivity to etcd. (auto-enabled if managed=true)boolfalse
etcd.tolerationsNode tolerations for cilium-etcd-operator scheduling to nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[{“operator”:”Exists”}]
etcd.updateStrategycilium-etcd-operator update strategyobject{“rollingUpdate”:{“maxSurge”:1,”maxUnavailable”:1},”type”:”RollingUpdate”}
externalIPs.enabledEnable ExternalIPs service support.boolfalse
externalWorkloadsConfigure external workloads supportobject{“enabled”:false}
externalWorkloads.enabledEnable support for external workloads, such as VMs (false by default).boolfalse
extraArgsAdditional agent container arguments.object{}
extraConfigextraConfig allows you to specify additional configuration parameters to be included in the cilium-config configmap.object{}
extraConfigmapMountsAdditional agent ConfigMap mounts.list[]
extraEnvAdditional agent container environment variables.object{}
extraHostPathMountsAdditional agent hostPath mounts.list[]
extraInitContainersAdditional InitContainers to initialize the pod.list[]
flannel.enabled boolfalse
flannel.masterDevice string“cni0”
flannel.uninstallOnExit boolfalse
gke.enabledEnable Google Kubernetes Engine integrationboolfalse
healthCheckingEnable connectivity health checking.booltrue
healthPortTCP port for the agent health API. This is not the port for cilium-health.int9876
hostFirewallEnables the enforcement of host policies in the eBPF datapath.boolfalse
hostPort.enabledEnable hostPort service support.boolfalse
hostServicesConfigure ClusterIP service handling in the host namespace (the node).object{“enabled”:false,”protocols”:”tcp,udp”}
hostServices.enabledEnable host reachable services.boolfalse
hostServices.protocolsSupported list of protocols to apply ClusterIP translation to.string“tcp,udp”
hubble.enabledEnable Hubble (true by default).booltrue
hubble.listenAddressAn additional address for Hubble to listen to. Set this field “:4244” if you are enabling Hubble Relay, as it assumes that Hubble is listening on port 4244.string“:4244”
hubble.metricsHubble metrics configuration. See https://docs.cilium.io/en/stable/configuration/metrics/#hubble-metrics for more comprehensive documentation about Hubble metrics.object{“enabled”:null,”port”:9091,”serviceMonitor”:{“enabled”:false}}
hubble.metrics.enabledConfigures the list of metrics to collect. If empty or null, metrics are disabled. Example: enabled: - dns:query;ignoreAAAA - drop - tcp - flow - icmp - http You can specify the list of metrics from the helm CLI: –set metrics.enabled=”{dns:query;ignoreAAAA,drop,tcp,flow,icmp,http}”stringnil
hubble.metrics.portConfigure the port the hubble metric server listens on.int9091
hubble.metrics.serviceMonitor.enabledCreate ServiceMonitor resources for Prometheus Operator. This requires the prometheus CRDs to be available. ref: https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)boolfalse
hubble.relay.dialTimeoutDial timeout to connect to the local hubble instance to receive peer information (e.g. “30s”).stringnil
hubble.relay.enabledEnable Hubble Relay (requires hubble.enabled=true)boolfalse
hubble.relay.imageHubble-relay container image.object{“digest”:”sha256:77379a9c25f5a613fcaaf5f8ce7e3d6e30576af483047800af6d8b6ca9b7bdb7”,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/hubble-relay”,”tag”:”v1.9.8”,”useDigest”:false}
hubble.relay.listenHostHost to listen to. Specify an empty string to bind to all the interfaces.string“”
hubble.relay.listenPortPort to listen to.string“4245”
hubble.relay.nodeSelectorNode labels for pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
hubble.relay.podAnnotationsAnnotations to be added to hubble-relay podsobject{}
hubble.relay.podLabelsLabels to be added to hubble-relay podsobject{}
hubble.relay.replicasNumber of replicas run for the hubble-relay deployment.int1
hubble.relay.resourcesSpecifies the resources for the hubble-relay podsobject{}
hubble.relay.retryTimeoutBackoff duration to retry connecting to the local hubble instance in case of failure (e.g. “30s”).stringnil
hubble.relay.rollOutPodsRoll out Hubble Relay pods automatically when configmap is updated.boolfalse
hubble.relay.sortBufferDrainTimeoutWhen the per-request flows sort buffer is not full, a flow is drained every time this timeout is reached (only affects requests in follow-mode) (e.g. “1s”).stringnil
hubble.relay.sortBufferLenMaxMax number of flows that can be buffered for sorting before being sent to the client (per request) (e.g. 100).stringnil
hubble.relay.tlsTLS configuration for Hubble Relayobject{“client”:{“cert”:””,”key”:””},”server”:{“cert”:””,”enabled”:false,”key”:””}}
hubble.relay.tls.clientbase64 encoded PEM values for the hubble-relay client certificate and private key This keypair is presented to Hubble server instances for mTLS authentication and is required when hubble.tls.enabled is true. These values need to be set manually if hubble.tls.auto.enabled is false.object{“cert”:””,”key”:””}
hubble.relay.tls.serverbase64 encoded PEM values for the hubble-relay server certificate and private keyobject{“cert”:””,”enabled”:false,”key”:””}
hubble.relay.tolerationsNode tolerations for pod assignment on nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[]
hubble.relay.updateStrategyhubble-relay update strategyobject{“rollingUpdate”:{“maxUnavailable”:1},”type”:”RollingUpdate”}
hubble.socketPathUnix domain socket path to listen to when Hubble is enabled.string“/var/run/cilium/hubble.sock”
hubble.tlsTLS configuration for Hubbleobject{“auto”:{“certValidityDuration”:1095,”enabled”:true,”method”:”helm”,”schedule”:”0 0 1 /4 “},”ca”:{“cert”:””,”key”:””},”enabled”:true,”server”:{“cert”:””,”key”:””}}
hubble.tls.autoConfigure automatic TLS certificates generation.object{“certValidityDuration”:1095,”enabled”:true,”method”:”helm”,”schedule”:”0 0 1 /4 “}
hubble.tls.auto.certValidityDurationGenerated certificates validity duration in days.int1095
hubble.tls.auto.enabledAuto-generate certificates. When set to true, automatically generate a CA and certificates to enable mTLS between Hubble server and Hubble Relay instances. If set to false, the certs for Hubble server need to be provided by setting appropriate values below.booltrue
hubble.tls.auto.methodSet the method to auto-generate certificates. Supported values: - helm: This method uses Helm to generate all certificates. - cronJob: This method uses a Kubernetes CronJob the generate any certificates not provided by the user at installation time.string“helm”
hubble.tls.auto.scheduleSchedule for certificates regeneration (regardless of their expiration date). Only used if method is “cronJob”. If nil, then no recurring job will be created. Instead, only the one-shot job is deployed to generate the certificates at installation time. Defaults to midnight of the first day of every fourth month. For syntax, see https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/#schedulestring“0 0 1 /4 “
hubble.tls.cabase64 encoded PEM values for the Hubble CA certificate and private key.object{“cert”:””,”key”:””}
hubble.tls.ca.keyThe CA private key (optional). If it is provided, then it will be used by hubble.tls.auto.method=cronJob to generate all other certificates. Otherwise, a ephemeral CA is generated if hubble.tls.auto.enabled=true.string“”
hubble.tls.enabledEnable mutual TLS for listenAddress. Setting this value to false is highly discouraged as the Hubble API provides access to potentially sensitive network flow metadata and is exposed on the host network.booltrue
hubble.tls.serverbase64 encoded PEM values for the Hubble server certificate and private keyobject{“cert”:””,”key”:””}
hubble.ui.backend.imageHubble-ui backend image.object{“pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/hubble-ui-backend”,”tag”:”v0.7.3”}
hubble.ui.backend.resourcesResource requests and limits for the ‘backend’ container of the ‘hubble-ui’ deployment.object{}
hubble.ui.enabledWhether to enable the Hubble UI.boolfalse
hubble.ui.frontend.imageHubble-ui frontend image.object{“pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/hubble-ui”,”tag”:”v0.7.3”}
hubble.ui.frontend.resourcesResource requests and limits for the ‘frontend’ container of the ‘hubble-ui’ deployment.object{}
hubble.ui.ingresshubble-ui ingress configuration.object{“annotations”:{},”enabled”:false,”hosts”:[“chart-example.local”],”tls”:[]}
hubble.ui.nodeSelectorNode labels for pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
hubble.ui.podAnnotationsAnnotations to be added to hubble-ui podsobject{}
hubble.ui.podLabelsLabels to be added to hubble-ui podsobject{}
hubble.ui.proxy.imageHubble-ui ingress proxy image.object{“pullPolicy”:”IfNotPresent”,”repository”:”docker.io/envoyproxy/envoy”,”tag”:”v1.14.5”}
hubble.ui.proxy.resourcesResource requests and limits for the ‘proxy’ container of the ‘hubble-ui’ deployment.object{}
hubble.ui.replicasThe number of replicas of Hubble UI to deploy.int1
hubble.ui.rollOutPodsRoll out Hubble-ui pods automatically when configmap is updated.boolfalse
hubble.ui.securityContext.enabledWhether to set the security context on the Hubble UI pods.booltrue
hubble.ui.tolerationsNode tolerations for pod assignment on nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[]
hubble.ui.updateStrategyhubble-ui update strategy.object{“rollingUpdate”:{“maxUnavailable”:1},”type”:”RollingUpdate”}
identityAllocationModeMethod to use for identity allocation (crd or kvstore).string“crd”
imageAgent container image.object{“digest”:”sha256:5d4c175a599ccb22a97dbc8b393a81caca71ada49951c5b5545039c6548ea350”,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/cilium”,”tag”:”v1.9.8”,”useDigest”:false}
imagePullSecretsConfigure image pull secrets for pulling container imagesstringnil
installIptablesRulesConfigure whether to install iptables rules to allow for TPROXY (L7 proxy injection), iptables-based masquerading and compatibility with kube-proxy.booltrue
ipMasqAgentConfigure the eBPF-based ip-masq-agentobject{“enabled”:false}
ipam.modeConfigure IP Address Management mode. ref: https://docs.cilium.io/en/stable/concepts/networking/ipam/string“cluster-pool”
ipam.operator.clusterPoolIPv4MaskSizeIPv4 CIDR mask size to delegate to individual nodes for IPAM.int24
ipam.operator.clusterPoolIPv4PodCIDRIPv4 CIDR range to delegate to individual nodes for IPAM.string“10.0.0.0/8”
ipam.operator.clusterPoolIPv6MaskSizeIPv6 CIDR mask size to delegate to individual nodes for IPAM.int120
ipam.operator.clusterPoolIPv6PodCIDRIPv6 CIDR range to delegate to individual nodes for IPAM.string“fd00::/104”
ipv4.enabledEnable IPv4 support.booltrue
ipv6.enabledEnable IPv6 support.boolfalse
ipvlan.enabledEnable the IPVLAN datapathboolfalse
k8sConfigure Kubernetes specific configurationobject{}
keepDeprecatedLabelsKeep the deprecated selector labels when deploying Cilium DaemonSet.boolfalse
keepDeprecatedProbesKeep the deprecated probes when deploying Cilium DaemonSetboolfalse
kubeProxyReplacementConfigure the kube-proxy replacement in Cilium BPF datapath Valid options are “disabled”, “probe”, “partial”, “strict”. ref: https://docs.cilium.io/en/stable/gettingstarted/kubeproxy-free/string“probe”
kubeProxyReplacementHealthzBindAddrhealthz server bind address for the kube-proxy replacement. To enable set the value to ‘0.0.0.0:10256’ for all ipv4 addresses and this ‘[::]:10256’ for all ipv6 addresses. By default it is disabled.string“”
l7ProxyEnable Layer 7 network policy.booltrue
localRedirectPolicyEnable Local Redirect Policy.boolfalse
logSystemLoadEnables periodic logging of system loadboolfalse
maglevConfigure maglev consistent hashingobject{}
masqueradeEnables masquerading of traffic leaving the node for destinations outside of the cluster.booltrue
monitorSpecify the CIDR for native routing (ie to avoid IP masquerade for). This value corresponds to the configured cluster-cidr. nativeRoutingCIDR:object{“enabled”:false}
monitor.enabledEnable the cilium-monitor sidecar.boolfalse
nameAgent container name.string“cilium”
nodePortConfigure service load balancing loadBalancer: algorithm is the name of the load balancing algorithm for backend selection e.g. random or maglev algorithm: “random” mode is the operation mode of load balancing for remote backends e.g. snat, dsr, hybrid mode: snat acceleration is the option to accelerate service handling via XDP e.g. native, disabled acceleration: disabledobject{“autoProtectPortRange”:true,”bindProtection”:true,”enableHealthCheck”:true,”enabled”:false}
nodePort.autoProtectPortRangeAppend NodePort range to ip_local_reserved_ports if clash with ephemeral ports is detected.booltrue
nodePort.bindProtectionSet to true to prevent applications binding to service ports.booltrue
nodePort.enableHealthCheckEnable healthcheck nodePort server for NodePort servicesbooltrue
nodePort.enabledEnable the Cilium NodePort service implementation.boolfalse
nodeinit.bootstrapFilebootstrapFile is the location of the file where the bootstrap timestamp is written by the node-init DaemonSetstring“/tmp/cilium-bootstrap-time”
nodeinit.enabledEnable the node initialization DaemonSetboolfalse
nodeinit.extraArgsAdditional nodeinit arguments.object{}
nodeinit.extraConfigmapMountsAdditional nodeinit ConfigMap mounts.list[]
nodeinit.extraEnvAdditional nodeinit environment variables.object{}
nodeinit.extraHostPathMountsAdditional nodeinit host path mounts.list[]
nodeinit.extraInitContainersAdditional nodeinit init containers.list[]
nodeinit.imagenode-init image.object{“pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/startup-script”,”tag”:”62bfbe88c17778aad7bef9fa57ff9e2d4a9ba0d8”}
nodeinit.nodeSelectorNode labels for nodeinit pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
nodeinit.podAnnotationsAnnotations to be added to node-init pods.object{}
nodeinit.podDisruptionBudgetPodDisruptionBudget settings ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/object{“enabled”:true,”maxUnavailable”:2}
nodeinit.podLabelsLabels to be added to node-init pods.object{}
nodeinit.priorityClassNameThe priority class to use for the nodeinit pod.string“”
nodeinit.resourcesnodeinit resource limits & requests ref: https://kubernetes.io/docs/user-guide/compute-resources/object{“requests”:{“cpu”:”100m”,”memory”:”100Mi”}}
nodeinit.securityContextSecurity context to be added to nodeinit pods.object{}
nodeinit.tolerationsNode tolerations for nodeinit scheduling to nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[{“operator”:”Exists”}]
nodeinit.updateStrategynode-init update strategyobject{“type”:”RollingUpdate”}
operator.affinitycilium-operator affinityobject{“podAntiAffinity”:{“requiredDuringSchedulingIgnoredDuringExecution”:[{“labelSelector”:{“matchExpressions”:[{“key”:”io.cilium/app”,”operator”:”In”,”values”:[“operator”]}]},”topologyKey”:”kubernetes.io/hostname”}]}}
operator.enabledEnable the cilium-operator component (required).booltrue
operator.endpointGCIntervalInterval for endpoint garbage collection.string“5m0s”
operator.extraArgsAdditional cilium-operator container argumentsobject{}
operator.extraConfigmapMountsAdditional cilium-operator ConfigMap mounts.list[]
operator.extraEnvAdditional cilium-operator environment variables.object{}
operator.extraHostPathMountsAdditional cilium-operator hostPath mounts.list[]
operator.extraInitContainersAdditional InitContainers to initialize the pod.list[]
operator.identityGCIntervalInterval for identity garbage collection.string“15m0s”
operator.identityHeartbeatTimeoutTimeout for identity heartbeats.string“30m0s”
operator.imagecilium-operator image.object{“awsDigest”:”sha256:ca21ab744f1fd8080e7bd7682b697c466cf9275fb88f56c888ee07601b6555ac”,”azureDigest”:”sha256:dcca7242c84c40e1284ee5d85361e1686b0bc934e94ab1e9f063e61916f7d0e1”,”genericDigest”:”sha256:e6c5e785c0695815d2f8ef1a99674af3d6453848f9feb2052c06af69348b3715”,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/operator”,”suffix”:””,”tag”:”v1.9.8”,”useDigest”:false}
operator.nodeSelectorNode labels for cilium-operator pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
operator.podAnnotationsAnnotations to be added to cilium-operator podsobject{}
operator.podDisruptionBudgetPodDisruptionBudget settings ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/object{“enabled”:false,”maxUnavailable”:1}
operator.podLabelsLabels to be added to cilium-operator podsobject{}
operator.priorityClassNamecilium-operator priorityClassNamestring“”
operator.prometheusEnable prometheus metrics for cilium-operator on the configured port at /metricsobject{“enabled”:false,”port”:6942,”serviceMonitor”:{“enabled”:false}}
operator.prometheus.serviceMonitor.enabledEnable service monitors. This requires the prometheus CRDs to be available (see https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)boolfalse
operator.replicasNumber of replicas to run for the cilium-operator deploymentint2
operator.resourcescilium-operator resource limits & requests ref: https://kubernetes.io/docs/user-guide/compute-resources/object{}
operator.rollOutPodsRoll out cilium-operator pods automatically when configmap is updated.boolfalse
operator.securityContextSecurity context to be added to cilium-operator podsobject{}
operator.tolerationsNode tolerations for cilium-operator scheduling to nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[{“operator”:”Exists”}]
operator.updateStrategycilium-operator update strategyobject{“rollingUpdate”:{“maxSurge”:1,”maxUnavailable”:1},”type”:”RollingUpdate”}
podAnnotationsAnnotations to be added to agent podsobject{}
podDisruptionBudgetPodDisruptionBudget settings ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/object{“enabled”:true,”maxUnavailable”:2}
podLabelsLabels to be added to agent podsobject{}
policyEnforcementModeThe agent can be put into one of the three policy enforcement modes: default, always and never. ref: https://docs.cilium.io/en/stable/policy/intro/#policy-enforcement-modesstring“default”
pprof.enabledEnable Go pprof debuggingboolfalse
preflight.enabledEnable Cilium pre-flight resources (required for upgrade)boolfalse
preflight.extraArgsAdditional preflight arguments.object{}
preflight.extraConfigmapMountsAdditional preflight ConfigMap mounts.list[]
preflight.extraEnvAdditional preflight environment variables.object{}
preflight.extraHostPathMountsAdditional preflight host path mounts.list[]
preflight.extraInitContainersAdditional preflight init containers.list[]
preflight.imageCilium pre-flight image.object{“digest”:”sha256:5d4c175a599ccb22a97dbc8b393a81caca71ada49951c5b5545039c6548ea350”,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/cilium”,”tag”:”v1.9.8”,”useDigest”:false}
preflight.nodeSelectorNode labels for preflight pod assignment ref: https://kubernetes.io/docs/user-guide/node-selection/object{}
preflight.podAnnotationsAnnotations to be added to preflight podsobject{}
preflight.podDisruptionBudgetPodDisruptionBudget settings ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/object{“enabled”:true,”maxUnavailable”:2}
preflight.podLabelsLabels to be added to the preflight pod.object{}
preflight.priorityClassNameThe priority class to use for the preflight pod.string“”
preflight.resourcespreflight resource limits & requests ref: https://kubernetes.io/docs/user-guide/compute-resources/object{}
preflight.securityContextSecurity context to be added to preflight podsobject{}
preflight.tofqdnsPreCachePath to write the —tofqdns-pre-cache file to.string“”
preflight.tolerationsNode tolerations for preflight scheduling to nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[{“effect”:”NoSchedule”,”key”:”node.kubernetes.io/not-ready”},{“effect”:”NoSchedule”,”key”:”node-role.kubernetes.io/master”},{“effect”:”NoSchedule”,”key”:”node.cloudprovider.kubernetes.io/uninitialized”,”value”:”true”},{“key”:”CriticalAddonsOnly”,”operator”:”Exists”}]
preflight.updateStrategypreflight update strategyobject{“type”:”RollingUpdate”}
preflight.validateCNPsBy default we should always validate the installed CNPs before upgrading Cilium. This will make sure the user will have the policies deployed in the cluster with the right schema.booltrue
priorityClassNameThe priority class to use for cilium-agent.string“”
prometheusConfigure prometheus metrics on the configured port at /metricsobject{“enabled”:false,”port”:9090,”serviceMonitor”:{“enabled”:false}}
prometheus.serviceMonitor.enabledEnable service monitors. This requires the prometheus CRDs to be available (see https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)boolfalse
proxyConfigure Istio proxy options.object{“prometheus”:{“port”:”9095”},”sidecarImageRegex”:”cilium/istio_proxy”}
proxy.sidecarImageRegexRegular expression matching compatible Istio sidecar istio-proxy container image namesstring“cilium/istio_proxy”
rbac.createEnable creation of Resource-Based Access Control configuration.booltrue
remoteNodeIdentityEnable use of the remote node identity. ref: https://docs.cilium.io/en/v1.7/install/upgrade/#configmap-remote-node-identitybooltrue
resourceQuotasEnable resource quotas for priority classes used in the cluster.object{“cilium”:{“hard”:{“pods”:”10k”}},”enabled”:false,”operator”:{“hard”:{“pods”:”15”}}}
resourcesAgent resource limits & requests ref: https://kubernetes.io/docs/user-guide/compute-resources/object{}
rollOutCiliumPodsRoll out cilium agent pods automatically when configmap is updated.boolfalse
securityContextSecurity context to be added to agent podsobject{}
serviceAccountsDefine serviceAccount names for components.objectComponent’s fully qualified name.
serviceAccounts.certgenCertgen is used if hubble.tls.auto.method=cronJobobject{“annotations”:{},”create”:true}
sleepAfterInitDo not run Cilium agent when running with clean mode. Useful to completely uninstall Cilium as it will stop Cilium from starting and create artifacts in the node.boolfalse
sockopsConfigure BPF socket operations configurationobject{“enabled”:false}
tlsConfigure TLS configuration in the agent.object{“enabled”:true,”secretsBackend”:”local”}
tolerationsNode tolerations for agent scheduling to nodes with taints ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/list[{“operator”:”Exists”}]
tunnelConfigure the encapsulation configuration for communication between nodes. Possible values: - disabled - vxlan (default) - genevestring“vxlan”
updateStrategyCilium agent update strategyobject{“rollingUpdate”:{“maxUnavailable”:2},”type”:”RollingUpdate”}
wellKnownIdentities.enabledEnable the use of well-known identities.boolfalse