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{“nodeAffinity”:{“requiredDuringSchedulingIgnoredDuringExecution”:{“nodeSelectorTerms”:[{“matchExpressions”:[{“key”:”kubernetes.io/os”,”operator”:”In”,”values”:[“linux”]}]},{“matchExpressions”:[{“key”:”beta.kubernetes.io/os”,”operator”:”In”,”values”:[“linux”]}]}]}},”podAntiAffinity”:{“requiredDuringSchedulingIgnoredDuringExecution”:[{“labelSelector”:{“matchExpressions”:[{“key”:”k8s-app”,”operator”:”In”,”values”:[“cilium”]}]},”topologyKey”:”kubernetes.io/hostname”}]}}
agentInstall the cilium agent resources.booltrue
agentNotReadyTaintKeyConfigure the key of the taint indicating that Cilium is not ready on the node. When set to a value starting with ignore-taint.cluster-autoscaler.kubernetes.io/, the Cluster Autoscaler will ignore the taint on its decisions, allowing the cluster to scale up.string“node.cilium.io/agent-not-ready”
aksbyocni.enabledEnable AKS BYOCNI integration. Note that this is incompatible with AKS clusters not created in BYOCNI mode: use Azure integration (azure.enabled) instead.boolfalse
alibabacloud.enabledEnable AlibabaCloud ENI integrationboolfalse
annotateK8sNodeAnnotate k8s node upon initialization with Cilium’s metadata.booltrue
autoDirectNodeRoutesEnable installation of PodCIDR routes between worker nodes if worker nodes share a common L2 network segment.boolfalse
azure.enabledEnable Azure integration. Note that this is incompatible with AKS clusters created in BYOCNI mode: use AKS BYOCNI integration (aksbyocni.enabled) instead.boolfalse
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
bgpConfigure BGPobject{“announce”:{“loadbalancerIP”:false,”podCIDR”:false},”enabled”:false}
bgp.announce.loadbalancerIPEnable allocation and announcement of service LoadBalancer IPsboolfalse
bgp.announce.podCIDREnable announcement of node pod CIDRboolfalse
bgp.enabledEnable BGP support inside Cilium; embeds a new ConfigMap for BGP inside cilium-agent and cilium-operatorboolfalse
bpf.clockProbeEnable BPF clock source probing for more efficient tick retrieval.boolfalse
bpf.lbExternalClusterIPAllow cluster external access to ClusterIP services.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
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”:{“override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/certgen”,”tag”:”v0.1.5@sha256:0c2b71bb3469990e7990e7e26243617aa344b5a69a4ce465740b8577f9d48ab9”},”podLabels”:{},”ttlSecondsAfterFinished”:1800}
certgen.podLabelsLabels to be added to hubble-certgen podsobject{}
certgen.ttlSecondsAfterFinishedSeconds after which the completed job pod will be deletedint1800
cgroupConfigure cgroup related configurationobject{“autoMount”:{“enabled”:true},”hostRoot”:”/run/cilium/cgroupv2”}
cgroup.autoMount.enabledEnable auto mount of cgroup2 filesystem. When autoMount is enabled, cgroup2 filesystem is mounted at cgroup.hostRoot path on the underlying host and inside the cilium agent pod. If users disable autoMount, it’s expected that users have mounted cgroup2 filesystem at the specified cgroup.hostRoot volume, and then the volume will be mounted inside the cilium agent pod at the same path.booltrue
cgroup.hostRootConfigure cgroup root where cgroup2 filesystem is mounted on the host (see also: cgroup.autoMount)string“/run/cilium/cgroupv2”
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{“override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/coreos/etcd”,”tag”:”v3.4.13@sha256:04833b601fa130512450afa45c4fe484fee1293634f34c7ddc231bd193c74017”}
clustermesh.apiserver.imageClustermesh API server image.object{“digest”:”sha256:faffaadeeed55779af31479a8b4663df4b5de2515018127a919409e3281e1b6f”,”override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/clustermesh-apiserver”,”tag”:”v1.11.7”,”useDigest”:true}
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.priorityClassNameThe priority class to use for clustermesh-apiserverstring“”
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{“certManagerIssuerRef”:{},”certValidityDuration”:1095,”enabled”:true,”method”:”helm”}
clustermesh.apiserver.tls.auto.certManagerIssuerRefcertmanager issuer used when clustermesh.apiserver.tls.auto.method=certmanager. If not specified, a CA issuer will be created.object{}
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”:””,”extraDnsNames”:[],”extraIpAddresses”:[],”key”:””}
clustermesh.apiserver.tls.server.extraDnsNamesExtra DNS names added to certificate when it’s auto generatedlist[]
clustermesh.apiserver.tls.server.extraIpAddressesExtra IP addresses added to certificate when it’s auto generatedlist[]
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.configClustermesh explicit configuration.object{“clusters”:[],”domain”:”mesh.cilium.io”,”enabled”:false}
clustermesh.config.clustersList of clusters to be peered in the mesh.list[]
clustermesh.config.domainDefault dns domain for the Clustermesh API servers This is used in the case cluster addresses are not provided and IPs are used.string“mesh.cilium.io”
clustermesh.config.enabledEnable the Clustermesh explicit configuration.boolfalse
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.exclusiveMake Cilium take ownership over the /etc/cni/net.d directory on the node, renaming all non-Cilium CNI configurations to .cilium_bak. This ensures no Pods can be scheduled using other CNI plugins during Cilium agent downtime.booltrue
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”
customCallsTail call hooks for custom eBPF programs.object{“enabled”:false}
customCalls.enabledEnable tail call hooks for custom eBPF programs.boolfalse
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”. Deprecated, to be removed in v1.12.string“veth”
debug.enabledEnable debug loggingboolfalse
disableEndpointCRDDisable the usage of CiliumEndpoint CRD.string“false”
egressGatewayEnables egress gateway (beta) to redirect and SNAT the traffic that leaves the cluster.object{“enabled”:false}
enableCiliumEndpointSliceEnable CiliumEndpointSlice feature.boolfalse
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
enableIPv4MasqueradeEnables masquerading of IPv4 traffic leaving the node from endpoints.booltrue
enableIPv6MasqueradeEnables masquerading of IPv6 traffic leaving the node from endpoints.booltrue
enableK8sEventHandoverConfigures the use of the KVStore to optimize Kubernetes event handling by mirroring it into the KVstore for reduced overhead in large clusters.boolfalse
enableK8sTerminatingEndpointConfigure whether to enable auto detect of terminating state for endpoints in order to support graceful termination.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: https://docs.cilium.io/en/stable/operations/system_requirements/#linux-kernel.booltrue
encryption.enabledEnable transparent network encryption.boolfalse
encryption.interfaceDeprecated in favor of encryption.ipsec.interface. The interface to use for encrypted traffic. This option is only effective when encryption.type is set to ipsec.string“”
encryption.ipsec.interfaceThe interface to use for encrypted traffic.string“”
encryption.ipsec.keyFileName of the key file inside the Kubernetes secret configured via secretName.string“”
encryption.ipsec.mountPathPath to mount the secret inside the Cilium pod.string“”
encryption.ipsec.secretNameName of the Kubernetes secret containing the encryption keys.string“”
encryption.keyFileDeprecated in favor of encryption.ipsec.keyFile. Name of the key file inside the Kubernetes secret configured via secretName. This option is only effective when encryption.type is set to ipsec.string“keys”
encryption.mountPathDeprecated in favor of encryption.ipsec.mountPath. Path to mount the secret inside the Cilium pod. This option is only effective when encryption.type is set to ipsec.string“/etc/ipsec”
encryption.nodeEncryptionEnable encryption for pure node to node traffic. This option is only effective when encryption.type is set to ipsec.boolfalse
encryption.secretNameDeprecated in favor of encryption.ipsec.secretName. Name of the Kubernetes secret containing the encryption keys. This option is only effective when encryption.type is set to ipsec.string“cilium-ipsec-keys”
encryption.typeEncryption method. Can be either ipsec or wireguard.string“ipsec”
encryption.wireguard.userspaceFallbackEnables the fallback to the user-space implementation.boolfalse
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
endpointStatusEnable endpoint status. Status can be: policy, health, controllers, logs and / or state. For 2 or more options use a comma.object{“enabled”:false,”status”:””}
eni.awsReleaseExcessIPsRelease IPs not used from the ENIboolfalse
eni.ec2APIEndpointEC2 API endpoint to usestring“”
eni.enabledEnable Elastic Network Interface (ENI) integration.boolfalse
eni.eniTagsTags to apply to the newly created ENIsobject{}
eni.iamRoleIf using IAM role for Service Accounts will not try to inject identity values from cilium-aws kubernetes secret. Adds annotation to service account if managed by Helm. See https://github.com/aws/amazon-eks-pod-identity-webhookstring“”
eni.subnetIDsFilterFilter via subnet IDs which will dictate which subnets are going to be used to create new ENIs Important note: This requires that each instance has an ENI with a matching subnet attached when Cilium is deployed. If you only want to control subnets for ENIs attached by Cilium, use the CNI configuration file settings (cni.customConf) instead.string“”
eni.subnetTagsFilterFilter via tags (k=v) which will dictate which subnets are going to be used to create new ENIs Important note: This requires that each instance has an ENI with a matching subnet attached when Cilium is deployed. If you only want to control subnets for ENIs attached by Cilium, use the CNI configuration file settings (cni.customConf) instead.string“”
eni.updateEC2AdapterLimitViaAPIUpdate ENI Adapter limits from the EC2 APIboolfalse
etcd.clusterDomainCluster domain for cilium-etcd-operator.string“cluster.local”
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.list[]
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{“override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/cilium-etcd-operator”,”tag”:”v2.0.7@sha256:04b8327f7f992693c2cb483b999041ed8f92efc8e14f2a5f3ab95574a65ea2dc”}
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.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.priorityClassNameThe priority class to use for cilium-etcd-operatorstring“”
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.list[]
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[]
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.int9879
hostFirewallConfigure the host firewall.object{“enabled”:false}
hostFirewall.enabledEnables 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/operations/metrics/#hubble-metrics for more comprehensive documentation about Hubble metrics.object{“enabled”:null,”port”:9091,”serviceAnnotations”:{},”serviceMonitor”:{“annotations”:{},”enabled”:false,”labels”:{}}}
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.serviceAnnotationsAnnotations to be added to hubble-metrics service.object{}
hubble.metrics.serviceMonitor.annotationsAnnotations to add to ServiceMonitor hubbleobject{}
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.metrics.serviceMonitor.labelsLabels to add to ServiceMonitor hubbleobject{}
hubble.peerService.clusterDomainThe cluster domain to use to query the Hubble Peer service. It should be the local cluster.string“cluster.local”
hubble.peerService.enabledEnable a K8s Service for the Peer service, so that it can be accessed by a non-local clientbooltrue
hubble.peerService.targetPortTarget Port for the Peer service.int4244
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:df6248b57528eadcf2fac6a27b47bad629ce1c868457a9a2e4835a47e0f18bd3”,”override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/hubble-relay”,”tag”:”v1.11.7”,”useDigest”:true}
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.priorityClassNameThe priority class to use for hubble-relaystring“”
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,”extraDnsNames”:[],”extraIpAddresses”:[],”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,”extraDnsNames”:[],”extraIpAddresses”:[],”key”:””}
hubble.relay.tls.server.extraDnsNamesextra DNS names added to certificate when its auto genlist[]
hubble.relay.tls.server.extraIpAddressesextra IP addresses added to certificate when its auto genlist[]
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”:{“certManagerIssuerRef”:{},”certValidityDuration”:1095,”enabled”:true,”method”:”helm”,”schedule”:”0 0 1 /4 “},”ca”:{“cert”:””,”key”:””},”enabled”:true,”server”:{“cert”:””,”extraDnsNames”:[],”extraIpAddresses”:[],”key”:””}}
hubble.tls.autoConfigure automatic TLS certificates generation.object{“certManagerIssuerRef”:{},”certValidityDuration”:1095,”enabled”:true,”method”:”helm”,”schedule”:”0 0 1 /4 “}
hubble.tls.auto.certManagerIssuerRefcertmanager issuer used when hubble.tls.auto.method=certmanager. If not specified, a CA issuer will be created.object{}
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. - certmanager: This method use cert-manager to generate & rotate certificates.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”:””,”extraDnsNames”:[],”extraIpAddresses”:[],”key”:””}
hubble.tls.server.extraDnsNamesExtra DNS names added to certificate when it’s auto generatedlist[]
hubble.tls.server.extraIpAddressesExtra IP addresses added to certificate when it’s auto generatedlist[]
hubble.ui.backend.imageHubble-ui backend image.object{“override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/hubble-ui-backend”,”tag”:”v0.9.0@sha256:000df6b76719f607a9edefb9af94dfd1811a6f1b6a8a9c537cba90bf12df474b”}
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{“override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/hubble-ui”,”tag”:”v0.9.0@sha256:0ef04e9a29212925da6bdfd0ba5b581765e41a01f1cc30563cef9b30b457fea0”}
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.priorityClassNameThe priority class to use for hubble-uistring“”
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.standalone.enabledWhen true, it will allow installing the Hubble UI only, without checking dependencies. It is useful if a cluster already has cilium and Hubble relay installed and you just want Hubble UI to be deployed. When installed via helm, installing UI should be done via helm upgrade and when installed via the cilium cli, then cilium hubble enable —uiboolfalse
hubble.ui.standalone.tls.certsVolumeWhen deploying Hubble UI in standalone, with tls enabled for Hubble relay, it is required to provide a volume for mounting the client certificates.object{}
hubble.ui.tls.clientbase64 encoded PEM values used to connect to hubble-relay This keypair is presented to Hubble Relay instances for mTLS authentication and is required when hubble.relay.tls.server.enabled is true. These values need to be set manually if hubble.tls.auto.enabled is false.object{“cert”:””,”key”:””}
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:66a6f72a49e55e21278d07a99ff2cffa7565ed07f2578d54b5a92c1a492a6597”,”override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/cilium”,”tag”:”v1.11.7”,”useDigest”:true}
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
installNoConntrackIptablesRulesInstall Iptables rules to skip netfilter connection tracking on all pod traffic. This option is only effective when Cilium is running in direct routing and full KPR mode. Moreover, this option cannot be enabled when Cilium is running in a managed Kubernetes environment or in a chained CNI setup.boolfalse
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.clusterPoolIPv4PodCIDRDeprecated in favor of ipam.operator.clusterPoolIPv4PodCIDRList. IPv4 CIDR range to delegate to individual nodes for IPAM.string“10.0.0.0/8”
ipam.operator.clusterPoolIPv4PodCIDRListIPv4 CIDR list range to delegate to individual nodes for IPAM.list[]
ipam.operator.clusterPoolIPv6MaskSizeIPv6 CIDR mask size to delegate to individual nodes for IPAM.int120
ipam.operator.clusterPoolIPv6PodCIDRDeprecated in favor of ipam.operator.clusterPoolIPv6PodCIDRList. IPv6 CIDR range to delegate to individual nodes for IPAM.string“fd00::/104”
ipam.operator.clusterPoolIPv6PodCIDRListIPv6 CIDR list range to delegate to individual nodes for IPAM.list[]
ipv4.enabledEnable IPv4 support.booltrue
ipv6.enabledEnable IPv6 support.boolfalse
ipvlan.enabledEnable the IPVLAN datapath (deprecated)boolfalse
k8sConfigure Kubernetes specific configurationobject{}
keepDeprecatedLabelsKeep the deprecated selector labels when deploying Cilium DaemonSet.boolfalse
keepDeprecatedProbesKeep the deprecated probes when deploying Cilium DaemonSetboolfalse
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“”
l2NeighDiscovery.enabledEnable L2 neighbor discovery in the agentbooltrue
l2NeighDiscovery.refreshPeriodOverride the agent’s default neighbor resolution refresh period.string“30s”
l7ProxyEnable Layer 7 network policy.booltrue
livenessProbe.failureThresholdfailure threshold of liveness probeint10
livenessProbe.periodSecondsinterval between checks of the liveness probeint30
localRedirectPolicyEnable Local Redirect Policy.boolfalse
logSystemLoadEnables periodic logging of system loadboolfalse
maglevConfigure maglev consistent hashingobject{}
monitorSpecify the IPv4 CIDR for native routing (ie to avoid IP masquerade for). This value corresponds to the configured cluster-cidr. ipv4NativeRoutingCIDR:object{“enabled”:false}
monitor.enabledEnable the cilium-monitor sidecar.boolfalse
nameAgent container name.string“cilium”
nodePortConfigure N-S k8s service loadbalancingobject{“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.d/cilium-bootstrap-time”
nodeinit.enabledEnable the node initialization DaemonSetboolfalse
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{“override”:null,”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 arguments.list[]
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{“alibabacloudDigest”:”sha256:2d154ac2d9dc000fd8ffd4e79bf6f10e9053c326bb6f75ed02a93b91ed2e986c”,”awsDigest”:”sha256:a5c4e2b27e403976dfdbf5a12f9dc3dbfce6f4e265056965febc7e1aa37a50e4”,”azureDigest”:”sha256:b5676bfb80361c6365a31b7e19d59c7f1d3c350fb1cd08948b74bb28204a39b3”,”genericDigest”:”sha256:0f8ed5d815873d20848a360df3f2ebbd4116481ff817d3f295557801e0b45900”,”override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/operator”,”suffix”:””,”tag”:”v1.11.7”,”useDigest”:true}
operator.nodeGCIntervalInterval for cilium node garbage collection.string“5m0s”
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.priorityClassNameThe priority class to use for cilium-operatorstring“”
operator.prometheusEnable prometheus metrics for cilium-operator on the configured port at /metricsobject{“enabled”:false,”port”:6942,”serviceMonitor”:{“annotations”:{},”enabled”:false,”labels”:{}}}
operator.prometheus.serviceMonitor.annotationsAnnotations to add to ServiceMonitor cilium-operatorobject{}
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.prometheus.serviceMonitor.labelsLabels to add to ServiceMonitor cilium-operatorobject{}
operator.removeNodeTaintsRemove Cilium node taint from Kubernetes nodes that have a healthy Cilium pod running.booltrue
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.serviceAccountNameFor using with an existing serviceAccount.string“cilium-operator”
operator.setNodeNetworkStatusSet Node condition NetworkUnavailable to ‘false’ with the reason ‘CiliumIsUp’ for nodes that have a healthy Cilium pod.booltrue
operator.skipCRDCreationSkip CRDs creation for cilium-operatorboolfalse
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.unmanagedPodWatcher.intervalSecondsInterval, in seconds, to check if there are any pods that are not managed by Cilium.int15
operator.unmanagedPodWatcher.restartRestart any pod that are not managed by Cilium.booltrue
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.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:66a6f72a49e55e21278d07a99ff2cffa7565ed07f2578d54b5a92c1a492a6597”,”override”:null,”pullPolicy”:”IfNotPresent”,”repository”:”quay.io/cilium/cilium”,”tag”:”v1.11.7”,”useDigest”:true}
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,”metrics”:null,”port”:9090,”serviceMonitor”:{“annotations”:{},”enabled”:false,”labels”:{}}}
prometheus.metricsMetrics that should be enabled or disabled from the default metric list. (+metric_foo to enable metric_foo , -metric_bar to disable metric_bar). ref: https://docs.cilium.io/en/stable/operations/metrics/#exported-metricsstringnil
prometheus.serviceMonitor.annotationsAnnotations to add to ServiceMonitor cilium-agentobject{}
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
prometheus.serviceMonitor.labelsLabels to add to ServiceMonitor cilium-agentobject{}
proxyConfigure Istio proxy options.object{“prometheus”:{“enabled”:true,”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
readinessProbe.failureThresholdfailure threshold of readiness probeint3
readinessProbe.periodSecondsinterval between checks of the readiness probeint30
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.clustermeshcertgenClustermeshcertgen is used if clustermesh.apiserver.tls.auto.method=cronJobobject{“annotations”:{},”create”:true,”name”:”clustermesh-apiserver-generate-certs”}
serviceAccounts.hubblecertgenHubblecertgen is used if hubble.tls.auto.method=cronJobobject{“annotations”:{},”create”:true,”name”:”hubble-generate-certs”}
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}
startupProbe.failureThresholdfailure threshold of startup probe. 105 x 2s translates to the old behaviour of the readiness probe (120s delay + 30 x 3s)int105
startupProbe.periodSecondsinterval between checks of the startup probeint2
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