From e0d8f6cb8596ea324f4392b575c3d2b352c06f78 Mon Sep 17 00:00:00 2001 From: Junwei Zhao Date: Fri, 28 Apr 2023 11:31:56 +1000 Subject: [PATCH] correct datadog identication round 2 by rollback most of the changes --- manifests/datadog.yaml | 1342 ++++++++++++++++++++-------------------- 1 file changed, 671 insertions(+), 671 deletions(-) diff --git a/manifests/datadog.yaml b/manifests/datadog.yaml index 06ee737..c40b2ad 100644 --- a/manifests/datadog.yaml +++ b/manifests/datadog.yaml @@ -367,723 +367,723 @@ spec: ignoreAutoConfig: - redisdb - redis - ## This is the Datadog Cluster Agent implementation that handles cluster-wide - ## metrics more cleanly, separates concerns for better rbac, and implements - ## the external metrics API so you can autoscale HPAs based on datadog metrics - ## ref: https://docs.datadoghq.com/agent/kubernetes/cluster/ - clusterAgent: - # clusterAgent.enabled -- Set this to true to enable Datadog Cluster Agent - enabled: true + ## This is the Datadog Cluster Agent implementation that handles cluster-wide + ## metrics more cleanly, separates concerns for better rbac, and implements + ## the external metrics API so you can autoscale HPAs based on datadog metrics + ## ref: https://docs.datadoghq.com/agent/kubernetes/cluster/ + clusterAgent: + # clusterAgent.enabled -- Set this to true to enable Datadog Cluster Agent + enabled: true - ## Define the Datadog Cluster-Agent image to work with - image: - # clusterAgent.image.repository -- Cluster Agent image repository to use - repository: gcr.io/datadoghq/cluster-agent + ## Define the Datadog Cluster-Agent image to work with + image: + # clusterAgent.image.repository -- Cluster Agent image repository to use + repository: gcr.io/datadoghq/cluster-agent - # clusterAgent.image.tag -- Cluster Agent image tag to use - # # tag: 1.9.1 + # clusterAgent.image.tag -- Cluster Agent image tag to use + # # tag: 1.9.1 - # clusterAgent.image.pullPolicy -- Cluster Agent image pullPolicy - pullPolicy: IfNotPresent + # clusterAgent.image.pullPolicy -- Cluster Agent image pullPolicy + pullPolicy: IfNotPresent - # clusterAgent.image.pullSecrets -- Cluster Agent repository pullSecret (ex: specify docker registry credentials) - ## See https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod - pullSecrets: [] - # - name: "" + # clusterAgent.image.pullSecrets -- Cluster Agent repository pullSecret (ex: specify docker registry credentials) + ## See https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod + pullSecrets: [] + # - name: "" - # clusterAgent.securityContext -- Allows you to overwrite the default PodSecurityContext on the cluster-agent pods. - securityContext: {} + # clusterAgent.securityContext -- Allows you to overwrite the default PodSecurityContext on the cluster-agent pods. + securityContext: {} - # clusterAgent.command -- Command to run in the Cluster Agent container as entrypoint - command: [] + # clusterAgent.command -- Command to run in the Cluster Agent container as entrypoint + command: [] - # clusterAgent.token -- Cluster Agent token is a preshared key between node agents and cluster agent (autogenerated if empty, needs to be at least 32 characters a-zA-z) - token: "" + # clusterAgent.token -- Cluster Agent token is a preshared key between node agents and cluster agent (autogenerated if empty, needs to be at least 32 characters a-zA-z) + token: "" - # clusterAgent.tokenExistingSecret -- Existing secret name to use for Cluster Agent token - tokenExistingSecret: "" + # clusterAgent.tokenExistingSecret -- Existing secret name to use for Cluster Agent token + tokenExistingSecret: "" - # clusterAgent.replicas -- Specify the of cluster agent replicas, if > 1 it allow the cluster agent to work in HA mode. - replicas: 1 + # clusterAgent.replicas -- Specify the of cluster agent replicas, if > 1 it allow the cluster agent to work in HA mode. + replicas: 1 - ## Provide Cluster Agent Deployment pod(s) media configuration - rbac: - # clusterAgent.rbac.create -- If true, create & use RBAC resources - create: true + ## Provide Cluster Agent Deployment pod(s) media configuration + rbac: + # clusterAgent.rbac.create -- If true, create & use RBAC resources + create: true - # clusterAgent.rbac.serviceAccountName -- Specify service account name to use (usually pre-existing, created if create is true) - serviceAccountName: default + # clusterAgent.rbac.serviceAccountName -- Specify service account name to use (usually pre-existing, created if create is true) + serviceAccountName: default - # Enable the metricsProvider to be able to scale based on metrics in Datadog - metricsProvider: - # clusterAgent.metricsProvider.enabled -- Set this to true to enable Metrics Provider - enabled: false - - # clusterAgent.metricsProvider.wpaController -- Enable informer and controller of the watermark pod autoscaler - ## NOTE: You need to install the `WatermarkPodAutoscaler` CRD before - wpaController: false - - # clusterAgent.metricsProvider.useDatadogMetrics -- Enable usage of DatadogMetric CRD to autoscale on arbitrary Datadog queries - ## NOTE: You need to install the `DatadogMetric` CRD before - useDatadogMetrics: false - - # clusterAgent.metricsProvider.createReaderRbac -- Create `external-metrics-reader` RBAC automatically (to allow HPA to read data from Cluster Agent) - createReaderRbac: true - - # clusterAgent.metricsProvider.aggregator -- Define the aggregator the cluster agent will use to process the metrics. The options are (avg, min, max, sum) - aggregator: avg - - ## Configuration for the service for the cluster-agent metrics server - service: - # clusterAgent.metricsProvider.service.type -- Set type of cluster-agent metrics server service - type: ClusterIP - - # clusterAgent.metricsProvider.service.port -- Set port of cluster-agent metrics server service (Kubernetes >= 1.15) - port: 8443 - - # clusterAgent.env -- Set environment variables specific to Cluster Agent - ## The Cluster-Agent supports many additional environment variables - ## ref: https://docs.datadoghq.com/agent/cluster_agent/commands/#cluster-agent-options - env: [] - - admissionController: - # clusterAgent.admissionController.enabled -- Enable the admissionController to be able to inject APM/Dogstatsd config and standard tags (env, service, version) automatically into your pods - enabled: false - - # clusterAgent.admissionController.mutateUnlabelled -- Enable injecting config without having the pod label 'admission.datadoghq.com/enabled="true"' - mutateUnlabelled: false - - # clusterAgent.confd -- Provide additional cluster check configurations - ## Each key will become a file in /conf.d - ## ref: https://docs.datadoghq.com/agent/autodiscovery/ - confd: {} - # mysql.yaml: |- - # cluster_check: true - # instances: - # - server: '' - # port: 3306 - # user: datadog - # pass: '' - - # clusterAgent.resources -- Datadog cluster-agent resource requests and limits. - resources: - requests: - cpu: 100m - memory: 200Mi - limits: - cpu: 100m - memory: 200Mi - - # clusterAgent.priorityClassName -- Name of the priorityClass to apply to the Cluster Agent - priorityClassName: # system-cluster-critical - - # clusterAgent.nodeSelector -- Allow the Cluster Agent Deployment to be scheduled on selected nodes - ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector - ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ - nodeSelector: {} - - # clusterAgent.affinity -- Allow the Cluster Agent Deployment to schedule using affinity rules - ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity - affinity: {} - - # clusterAgent.healthPort -- Port number to use in the Cluster Agent for the healthz endpoint - healthPort: 5555 - - # clusterAgent.livenessProbe -- Override default Cluster Agent liveness probe settings - # @default -- Every 15s / 6 KO / 1 OK - livenessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - successThreshold: 1 - failureThreshold: 6 - - # clusterAgent.readinessProbe -- Override default Cluster Agent readiness probe settings - # @default -- Every 15s / 6 KO / 1 OK - readinessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - successThreshold: 1 - failureThreshold: 6 - - # clusterAgent.strategy -- Allow the Cluster Agent deployment to perform a rolling update on helm update - ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy - strategy: - type: RollingUpdate - rollingUpdate: - maxSurge: 1 - maxUnavailable: 0 - - # clusterAgent.podAnnotations -- Annotations to add to the cluster-agents's pod(s) - podAnnotations: {} - # key: "value" - - # clusterAgent.useHostNetwork -- Bind ports on the hostNetwork - ## Useful for CNI networking where hostPort might - ## not be supported. The ports need to be available on all hosts. It can be - ## used for custom metrics instead of a service endpoint. - ## - ## WARNING: Make sure that hosts using this are properly firewalled otherwise - ## metrics and traces are accepted from any host able to connect to this host. - # - useHostNetwork: # true - - # clusterAgent.dnsConfig -- Specify dns configuration options for datadog cluster agent containers e.g ndots - ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config - dnsConfig: {} - # options: - # - name: ndots - # value: "1" - - # clusterAgent.volumes -- Specify additional volumes to mount in the cluster-agent container - volumes: [] - # - hostPath: - # path: - # name: - - # clusterAgent.volumeMounts -- Specify additional volumes to mount in the cluster-agent container - volumeMounts: [] - # - name: - # mountPath: - # readOnly: true - - # clusterAgent.datadog_cluster_yaml -- Specify custom contents for the datadog cluster agent config (datadog-cluster.yaml) - datadog_cluster_yaml: {} - - # clusterAgent.createPodDisruptionBudget -- Create pod disruption budget for Cluster Agent deployments - createPodDisruptionBudget: false - - networkPolicy: - # clusterAgent.networkPolicy.create -- If true, create a NetworkPolicy for the cluster agent. - # DEPRECATED. Use datadog.networkPolicy.create instead - create: false - - # clusterAgent.additionalLabels -- Adds labels to the Cluster Agent deployment and pods - additionalLabels: {} - # key: "value" - - agents: - # agents.enabled -- You should keep Datadog DaemonSet enabled! - ## The exceptional case could be a situation when you need to run - ## single Datadog pod per every namespace, but you do not need to - ## re-create a DaemonSet for every non-default namespace install. - ## Note: StatsD and DogStatsD work over UDP, so you may not - ## get guaranteed delivery of the metrics in Datadog-per-namespace setup! - # - enabled: true - - ## Define the Datadog image to work with - image: - # agents.image.repository -- Datadog Agent image repository to use - ## use "gcr.io/datadoghq/agent" for Datadog Agent 7 - ## use "gcr.io/datadoghq/dogstatsd" for Standalone Datadog Agent DogStatsD 7 - repository: gcr.io/datadoghq/agent - - # agents.image.tag -- Define the Agent version to use - ## Use 7-jmx to enable jmx fetch collection - # tag: 7.34.0 - - # agents.image.doNotCheckTag -- Skip the version<>chart compatibility check - ## By default, the version passed in agents.image.tag is checked - ## for compatibility with the version of the chart. - ## This boolean permits to completely skip this check. - ## This is useful, for example, for custom tags that are not - ## respecting semantic versioning - doNotCheckTag: # false - - # agents.image.pullPolicy -- Datadog Agent image pull policy - pullPolicy: IfNotPresent - - # agents.image.pullSecrets -- Datadog Agent repository pullSecret (ex: specify docker registry credentials) - ## See https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod - pullSecrets: [] - # - name: "" - - ## Provide Daemonset RBAC configuration - rbac: - # agents.rbac.create -- If true, create & use RBAC resources - create: true - - # agents.rbac.serviceAccountName -- Specify service account name to use (usually pre-existing, created if create is true) - serviceAccountName: default - - ## Provide Daemonset PodSecurityPolicy configuration - podSecurity: - podSecurityPolicy: - # agents.podSecurity.podSecurityPolicy.create -- If true, create a PodSecurityPolicy resource for Agent pods - create: false - - securityContextConstraints: - # agents.podSecurity.securityContextConstraints.create -- If true, create a SecurityContextConstraints resource for Agent pods - create: false - - # agents.podSecurity.seLinuxContext -- Provide seLinuxContext configuration for PSP/SCC - # @default -- Must run as spc_t - seLinuxContext: - rule: MustRunAs - seLinuxOptions: - user: system_u - role: system_r - type: spc_t - level: s0 - - # agents.podSecurity.privileged -- If true, Allow to run privileged containers - privileged: true - - # agents.podSecurity.capabilites -- Allowed capabilites - capabilites: - - SYS_ADMIN - - SYS_RESOURCE - - SYS_PTRACE - - NET_ADMIN - - NET_BROADCAST - - IPC_LOCK - - AUDIT_CONTROL - - AUDIT_READ - - # agents.podSecurity.volumes -- Allowed volumes types - volumes: - - configMap - - downwardAPI - - emptyDir - - hostPath - - secret - - # agents.podSecurity.seccompProfiles -- Allowed seccomp profiles - seccompProfiles: - - "runtime/default" - - "localhost/system-probe" - - # agents.podSecurity.apparmorProfiles -- Allowed apparmor profiles - apparmorProfiles: - - "runtime/default" - - apparmor: - # agents.podSecurity.apparmor.enabled -- If true, enable apparmor enforcement - ## see: https://kubernetes.io/docs/tutorials/clusters/apparmor/ - enabled: true - - containers: - agent: - # agents.containers.agent.env -- Additional environment variables for the agent container - env: [] - - # agents.containers.agent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off - # agents.containers.agent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off - ## If not set, fall back to the value of datadog.logLevel. - logLevel: # INFO - - # agents.containers.agent.resources -- Resource requests and limits for the agent container. - resources: - requests: - cpu: 200m - memory: 256Mi - limits: - cpu: 200m - memory: 256Mi - - # agents.containers.agent.healthPort -- Port number to use in the node agent for the healthz endpoint - healthPort: 5555 - - # agents.containers.agent.livenessProbe -- Override default agent liveness probe settings - # @default -- Every 15s / 6 KO / 1 OK - livenessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - successThreshold: 1 - failureThreshold: 6 - - # agents.containers.agent.readinessProbe -- Override default agent readiness probe settings - # @default -- Every 15s / 6 KO / 1 OK - readinessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - successThreshold: 1 - failureThreshold: 6 - - # agents.containers.agent.securityContext -- Allows you to overwrite the default container SecurityContext for the agent container. - securityContext: {} - - processAgent: - # agents.containers.processAgent.env -- Additional environment variables for the process-agent container - env: [] - - # agents.containers.processAgent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off - ## If not set, fall back to the value of datadog.logLevel. - logLevel: # INFO - - # agents.containers.processAgent.resources -- Resource requests and limits for the process-agent container - resources: - requests: - cpu: 100m - memory: 200Mi - limits: - cpu: 100m - memory: 200Mi - - # agents.containers.processAgent.securityContext -- Allows you to overwrite the default container SecurityContext for the process-agent container. - securityContext: {} - - traceAgent: - # agents.containers.traceAgent.env -- Additional environment variables for the trace-agent container - env: - - # agents.containers.traceAgent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off - logLevel: # INFO - - # agents.containers.traceAgent.resources -- Resource requests and limits for the trace-agent container - resources: - requests: - cpu: 50m - memory: 100Mi - limits: - cpu: 50m - memory: 100Mi - - # agents.containers.traceAgent.livenessProbe -- Override default agent liveness probe settings - # @default -- Every 15s - livenessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - - # agents.containers.traceAgent.securityContext -- Allows you to overwrite the default container SecurityContext for the trace-agent container. - securityContext: {} - - systemProbe: - # agents.containers.systemProbe.env -- Additional environment variables for the system-probe container - env: [] - - # agents.containers.systemProbe.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off. - ## If not set, fall back to the value of datadog.logLevel. - logLevel: # INFO - - # agents.containers.systemProbe.resources -- Resource requests and limits for the system-probe container - resources: - requests: - cpu: 50m - memory: 100Mi - limits: - cpu: 50m - memory: 100Mi - - # agents.containers.systemProbe.securityContext -- Allows you to overwrite the default container SecurityContext for the system-probe container. - securityContext: - privileged: true - capabilities: - add: ["SYS_ADMIN", "SYS_RESOURCE", "SYS_PTRACE", "NET_ADMIN", "NET_BROADCAST", "IPC_LOCK"] - securityAgent: - # agents.containers.securityAgent.env -- Additional environment variables for the security-agent container - env: - - # agents.containers.securityAgent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off - ## If not set, fall back to the value of datadog.logLevel. - logLevel: # INFO - - # agents.containers.securityAgent.resources -- Resource requests and limits for the security-agent container - resources: - requests: - cpu: 100m - memory: 200Mi - limits: - cpu: 100m - memory: 200Mi - - initContainers: - # agents.containers.initContainers.resources -- Resource requests and limits for the init containers - resources: {} - # requests: - # cpu: 100m - # memory: 200Mi - # limits: - # cpu: 100m - # memory: 200Mi - - # agents.volumes -- Specify additional volumes to mount in the dd-agent container - volumes: [] - # - hostPath: - # path: - # name: - - # agents.volumeMounts -- Specify additional volumes to mount in all containers of the agent pod - volumeMounts: [] - # - name: - # mountPath: - # readOnly: true - - # agents.useHostNetwork -- Bind ports on the hostNetwork - ## Useful for CNI networking where hostPort might - ## not be supported. The ports need to be available on all hosts. It Can be - ## used for custom metrics instead of a service endpoint. - ## - ## WARNING: Make sure that hosts using this are properly firewalled otherwise - ## metrics and traces are accepted from any host able to connect to this host. - useHostNetwork: false - - # agents.dnsConfig -- specify dns configuration options for datadog cluster agent containers e.g ndots - ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config - dnsConfig: {} - # options: - # - name: ndots - # value: "1" - - # agents.podAnnotations -- Annotations to add to the DaemonSet's Pods - podAnnotations: {} - # : '[{"key": "", "value": ""}]' - - # agents.tolerations -- Allow the DaemonSet to schedule on tainted nodes (requires Kubernetes >= 1.6) - tolerations: - - effect: NoSchedule - operator: Exists - - # agents.nodeSelector -- Allow the DaemonSet to schedule on selected nodes - ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ - nodeSelector: {} - - # agents.affinity -- Allow the DaemonSet to schedule using affinity rules - ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity - affinity: {} - - # agents.updateStrategy -- Allow the DaemonSet to perform a rolling update on helm update - ## ref: https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/ - updateStrategy: - type: RollingUpdate - rollingUpdate: - maxUnavailable: "10%" - - # agents.priorityClassName -- Sets PriorityClassName if defineds - priorityClassName: - - # agents.podLabels -- Sets podLabels if defined - # Note: These labels are also used as label selectors so they are immutable. - podLabels: {} - - # agents.additionalLabels -- Adds labels to the Agent daemonset and pods - additionalLabels: {} - # key: "value" - - # agents.useConfigMap -- Configures a configmap to provide the agent configuration. Use this in combination with the `agents.customAgentConfig` parameter. - useConfigMap: # false - - # agents.customAgentConfig -- Specify custom contents for the datadog agent config (datadog.yaml) - ## ref: https://docs.datadoghq.com/agent/guide/agent-configuration-files/?tab=agentv6 - ## ref: https://github.com/DataDog/datadog-agent/blob/master/pkg/config/config_template.yaml - ## Note the `agents.useConfigMap` needs to be set to `true` for this parameter to be taken into account. - customAgentConfig: - # # Autodiscovery for Kubernetes - # listeners: - # - name: kubelet - # config_providers: - # - name: kubelet - # polling: true - # # needed to support legacy docker label config templates - # - name: docker - # polling: true - # - # Enable APM by setting the DD_APM_ENABLED envvar to true, or override this configuration - apm_config: - enabled: true - apm_non_local_traffic: true - # # Enable java cgroup handling. Only one of those options should be enabled, - # # depending on the agent version you are using along that chart. - # - # # agent version < 6.15 - # # jmx_use_cgroup_memory_limit: true - # - # # agent version >= 6.15 - # # jmx_use_container_support: true - - networkPolicy: - # agents.networkPolicy.create -- If true, create a NetworkPolicy for the agents. - # DEPRECATED. Use datadog.networkPolicy.create instead - create: false - - clusterChecksRunner: - # clusterChecksRunner.enabled -- If true, deploys agent dedicated for running the Cluster Checks instead of running in the Daemonset's agents. - ## ref: https://docs.datadoghq.com/agent/autodiscovery/clusterchecks/ + # Enable the metricsProvider to be able to scale based on metrics in Datadog + metricsProvider: + # clusterAgent.metricsProvider.enabled -- Set this to true to enable Metrics Provider enabled: false - ## Define the Datadog image to work with. - image: - # clusterChecksRunner.image.repository -- Datadog Agent image repository to use - ## use "gcr.io/datadoghq/agent" for Datadog Agent 7 - repository: gcr.io/datadoghq/agent + # clusterAgent.metricsProvider.wpaController -- Enable informer and controller of the watermark pod autoscaler + ## NOTE: You need to install the `WatermarkPodAutoscaler` CRD before + wpaController: false - # clusterChecksRunner.image.tag -- Define the Agent version to use - ## Use 7-jmx to enable jmx fetch collection - # tag: 7.24.1 + # clusterAgent.metricsProvider.useDatadogMetrics -- Enable usage of DatadogMetric CRD to autoscale on arbitrary Datadog queries + ## NOTE: You need to install the `DatadogMetric` CRD before + useDatadogMetrics: false - # clusterChecksRunner.image.pullPolicy -- Datadog Agent image pull policy - pullPolicy: IfNotPresent + # clusterAgent.metricsProvider.createReaderRbac -- Create `external-metrics-reader` RBAC automatically (to allow HPA to read data from Cluster Agent) + createReaderRbac: true - # clusterChecksRunner.image.pullSecrets -- Datadog Agent repository pullSecret (ex: specify docker registry credentials) - ## See https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod - pullSecrets: [] - # - name: "" + # clusterAgent.metricsProvider.aggregator -- Define the aggregator the cluster agent will use to process the metrics. The options are (avg, min, max, sum) + aggregator: avg - # clusterChecksRunner.createPodDisruptionBudget -- Create the pod disruption budget to apply to the cluster checks agents - createPodDisruptionBudget: false + ## Configuration for the service for the cluster-agent metrics server + service: + # clusterAgent.metricsProvider.service.type -- Set type of cluster-agent metrics server service + type: ClusterIP - # Provide Cluster Checks Deployment pods RBAC configuration - rbac: - # clusterChecksRunner.rbac.create -- If true, create & use RBAC resources - create: true + # clusterAgent.metricsProvider.service.port -- Set port of cluster-agent metrics server service (Kubernetes >= 1.15) + port: 8443 - # clusterChecksRunner.rbac.dedicated -- If true, use a dedicated RBAC resource for the cluster checks agent(s) - dedicated: false + # clusterAgent.env -- Set environment variables specific to Cluster Agent + ## The Cluster-Agent supports many additional environment variables + ## ref: https://docs.datadoghq.com/agent/cluster_agent/commands/#cluster-agent-options + env: [] - # clusterChecksRunner.rbac.serviceAccountAnnotations -- Annotations to add to the ServiceAccount if clusterChecksRunner.rbac.dedicated is true - serviceAccountAnnotations: {} + admissionController: + # clusterAgent.admissionController.enabled -- Enable the admissionController to be able to inject APM/Dogstatsd config and standard tags (env, service, version) automatically into your pods + enabled: false - # clusterChecksRunner.rbac.serviceAccountName -- Specify service account name to use (usually pre-existing, created if create is true) - serviceAccountName: default + # clusterAgent.admissionController.mutateUnlabelled -- Enable injecting config without having the pod label 'admission.datadoghq.com/enabled="true"' + mutateUnlabelled: false - # clusterChecksRunner.replicas -- Number of Cluster Checks Runner instances - ## If you want to deploy the clusterChecks agent in HA, keep at least clusterChecksRunner.replicas set to 2. - ## And increase the clusterChecksRunner.replicas according to the number of Cluster Checks. - replicas: 2 + # clusterAgent.confd -- Provide additional cluster check configurations + ## Each key will become a file in /conf.d + ## ref: https://docs.datadoghq.com/agent/autodiscovery/ + confd: {} + # mysql.yaml: |- + # cluster_check: true + # instances: + # - server: '' + # port: 3306 + # user: datadog + # pass: '' - # clusterChecksRunner.resources -- Datadog clusterchecks-agent resource requests and limits. - resources: - requests: - cpu: 100m - memory: 200Mi - limits: - cpu: 100m - memory: 200Mi + # clusterAgent.resources -- Datadog cluster-agent resource requests and limits. + resources: + requests: + cpu: 100m + memory: 200Mi + limits: + cpu: 100m + memory: 200Mi - # clusterChecksRunner.affinity -- Allow the ClusterChecks Deployment to schedule using affinity rules. - ## By default, ClusterChecks Deployment Pods are forced to run on different Nodes. - ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity - affinity: {} + # clusterAgent.priorityClassName -- Name of the priorityClass to apply to the Cluster Agent + priorityClassName: # system-cluster-critical - # clusterChecksRunner.strategy -- Allow the ClusterChecks deployment to perform a rolling update on helm update - ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy - strategy: - type: RollingUpdate - rollingUpdate: - maxSurge: 1 - maxUnavailable: 0 + # clusterAgent.nodeSelector -- Allow the Cluster Agent Deployment to be scheduled on selected nodes + ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector + ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ + nodeSelector: {} - # clusterChecksRunner.dnsConfig -- specify dns configuration options for datadog cluster agent containers e.g ndots - ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config - dnsConfig: {} - # options: - # - name: ndots - # value: "1" + # clusterAgent.affinity -- Allow the Cluster Agent Deployment to schedule using affinity rules + ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity + affinity: {} - # clusterChecksRunner.nodeSelector -- Allow the ClusterChecks Deployment to schedule on selected nodes - ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ - # - nodeSelector: {} + # clusterAgent.healthPort -- Port number to use in the Cluster Agent for the healthz endpoint + healthPort: 5555 - # clusterChecksRunner.tolerations -- Tolerations for pod assignment - ## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ - # - tolerations: [] + # clusterAgent.livenessProbe -- Override default Cluster Agent liveness probe settings + # @default -- Every 15s / 6 KO / 1 OK + livenessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + successThreshold: 1 + failureThreshold: 6 - # clusterChecksRunner.healthPort -- Port number to use in the Cluster Checks Runner for the healthz endpoint - healthPort: 5555 + # clusterAgent.readinessProbe -- Override default Cluster Agent readiness probe settings + # @default -- Every 15s / 6 KO / 1 OK + readinessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + successThreshold: 1 + failureThreshold: 6 - # clusterChecksRunner.livenessProbe -- Override default agent liveness probe settings - # @default -- Every 15s / 6 KO / 1 OK - ## In case of issues with the probe, you can disable it with the - ## following values, to allow easier investigating: - # - # livenessProbe: - # exec: - # command: ["/bin/true"] - # - livenessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - successThreshold: 1 - failureThreshold: 6 + # clusterAgent.strategy -- Allow the Cluster Agent deployment to perform a rolling update on helm update + ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy + strategy: + type: RollingUpdate + rollingUpdate: + maxSurge: 1 + maxUnavailable: 0 - # clusterChecksRunner.readinessProbe -- Override default agent readiness probe settings - # @default -- Every 15s / 6 KO / 1 OK - ## In case of issues with the probe, you can disable it with the - ## following values, to allow easier investigating: - # - # readinessProbe: - # exec: - # command: ["/bin/true"] - # - readinessProbe: - initialDelaySeconds: 15 - periodSeconds: 15 - timeoutSeconds: 5 - successThreshold: 1 - failureThreshold: 6 + # clusterAgent.podAnnotations -- Annotations to add to the cluster-agents's pod(s) + podAnnotations: {} + # key: "value" - # clusterChecksRunner.podAnnotations -- Annotations to add to the cluster-checks-runner's pod(s) - podAnnotations: {} - # key: "value" + # clusterAgent.useHostNetwork -- Bind ports on the hostNetwork + ## Useful for CNI networking where hostPort might + ## not be supported. The ports need to be available on all hosts. It can be + ## used for custom metrics instead of a service endpoint. + ## + ## WARNING: Make sure that hosts using this are properly firewalled otherwise + ## metrics and traces are accepted from any host able to connect to this host. + # + useHostNetwork: # true - # clusterChecksRunner.env -- Environment variables specific to Cluster Checks Runner - ## ref: https://github.com/DataDog/datadog-agent/tree/master/Dockerfiles/agent#environment-variables - env: - - name: DD_KUBELET_TLS_VERIFY - value: "false" + # clusterAgent.dnsConfig -- Specify dns configuration options for datadog cluster agent containers e.g ndots + ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config + dnsConfig: {} + # options: + # - name: ndots + # value: "1" - # clusterChecksRunner.volumes -- Specify additional volumes to mount in the cluster checks container - volumes: [] - # - hostPath: - # path: - # name: + # clusterAgent.volumes -- Specify additional volumes to mount in the cluster-agent container + volumes: [] + # - hostPath: + # path: + # name: - # clusterChecksRunner.volumeMounts -- Specify additional volumes to mount in the cluster checks container - volumeMounts: [] - # - name: - # mountPath: - # readOnly: true + # clusterAgent.volumeMounts -- Specify additional volumes to mount in the cluster-agent container + volumeMounts: [] + # - name: + # mountPath: + # readOnly: true - networkPolicy: - # clusterChecksRunner.networkPolicy.create -- If true, create a NetworkPolicy for the cluster checks runners. - # DEPRECATED. Use datadog.networkPolicy.create instead + # clusterAgent.datadog_cluster_yaml -- Specify custom contents for the datadog cluster agent config (datadog-cluster.yaml) + datadog_cluster_yaml: {} + + # clusterAgent.createPodDisruptionBudget -- Create pod disruption budget for Cluster Agent deployments + createPodDisruptionBudget: false + + networkPolicy: + # clusterAgent.networkPolicy.create -- If true, create a NetworkPolicy for the cluster agent. + # DEPRECATED. Use datadog.networkPolicy.create instead + create: false + + # clusterAgent.additionalLabels -- Adds labels to the Cluster Agent deployment and pods + additionalLabels: {} + # key: "value" + + agents: + # agents.enabled -- You should keep Datadog DaemonSet enabled! + ## The exceptional case could be a situation when you need to run + ## single Datadog pod per every namespace, but you do not need to + ## re-create a DaemonSet for every non-default namespace install. + ## Note: StatsD and DogStatsD work over UDP, so you may not + ## get guaranteed delivery of the metrics in Datadog-per-namespace setup! + # + enabled: true + + ## Define the Datadog image to work with + image: + # agents.image.repository -- Datadog Agent image repository to use + ## use "gcr.io/datadoghq/agent" for Datadog Agent 7 + ## use "gcr.io/datadoghq/dogstatsd" for Standalone Datadog Agent DogStatsD 7 + repository: gcr.io/datadoghq/agent + + # agents.image.tag -- Define the Agent version to use + ## Use 7-jmx to enable jmx fetch collection + # tag: 7.34.0 + + # agents.image.doNotCheckTag -- Skip the version<>chart compatibility check + ## By default, the version passed in agents.image.tag is checked + ## for compatibility with the version of the chart. + ## This boolean permits to completely skip this check. + ## This is useful, for example, for custom tags that are not + ## respecting semantic versioning + doNotCheckTag: # false + + # agents.image.pullPolicy -- Datadog Agent image pull policy + pullPolicy: IfNotPresent + + # agents.image.pullSecrets -- Datadog Agent repository pullSecret (ex: specify docker registry credentials) + ## See https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod + pullSecrets: [] + # - name: "" + + ## Provide Daemonset RBAC configuration + rbac: + # agents.rbac.create -- If true, create & use RBAC resources + create: true + + # agents.rbac.serviceAccountName -- Specify service account name to use (usually pre-existing, created if create is true) + serviceAccountName: default + + ## Provide Daemonset PodSecurityPolicy configuration + podSecurity: + podSecurityPolicy: + # agents.podSecurity.podSecurityPolicy.create -- If true, create a PodSecurityPolicy resource for Agent pods create: false - # clusterChecksRunner.additionalLabels -- Adds labels to the cluster checks runner deployment and pods - additionalLabels: {} - # key: "value" + securityContextConstraints: + # agents.podSecurity.securityContextConstraints.create -- If true, create a SecurityContextConstraints resource for Agent pods + create: false - # clusterChecksRunner.securityContext -- Allows you to overwrite the default PodSecurityContext on the clusterchecks pods. - securityContext: {} + # agents.podSecurity.seLinuxContext -- Provide seLinuxContext configuration for PSP/SCC + # @default -- Must run as spc_t + seLinuxContext: + rule: MustRunAs + seLinuxOptions: + user: system_u + role: system_r + type: spc_t + level: s0 - datadog-crds: - crds: - # datadog-crds.crds.datadogMetrics -- Set to true to deploy the DatadogMetrics CRD - datadogMetrics: true + # agents.podSecurity.privileged -- If true, Allow to run privileged containers + privileged: true - kube-state-metrics: - rbac: - # kube-state-metrics.rbac.create -- If true, create & use RBAC resources - create: true + # agents.podSecurity.capabilites -- Allowed capabilites + capabilites: + - SYS_ADMIN + - SYS_RESOURCE + - SYS_PTRACE + - NET_ADMIN + - NET_BROADCAST + - IPC_LOCK + - AUDIT_CONTROL + - AUDIT_READ - serviceAccount: - # kube-state-metrics.serviceAccount.create -- If true, create ServiceAccount, require rbac kube-state-metrics.rbac.create true - create: true + # agents.podSecurity.volumes -- Allowed volumes types + volumes: + - configMap + - downwardAPI + - emptyDir + - hostPath + - secret - # kube-state-metrics.serviceAccount.name -- The name of the ServiceAccount to use. - ## If not set and create is true, a name is generated using the fullname template - name: datadog-kube-state-metrics + # agents.podSecurity.seccompProfiles -- Allowed seccomp profiles + seccompProfiles: + - "runtime/default" + - "localhost/system-probe" - # kube-state-metrics.resources -- Resource requests and limits for the kube-state-metrics container. - resources: - requests: - cpu: 100m - memory: 256Mi - limits: - cpu: 100m - memory: 256Mi + # agents.podSecurity.apparmorProfiles -- Allowed apparmor profiles + apparmorProfiles: + - "runtime/default" - # kube-state-metrics.nodeSelector -- Node selector for KSM. KSM only supports Linux. - nodeSelector: - kubernetes.io/os: linux + apparmor: + # agents.podSecurity.apparmor.enabled -- If true, enable apparmor enforcement + ## see: https://kubernetes.io/docs/tutorials/clusters/apparmor/ + enabled: true + + containers: + agent: + # agents.containers.agent.env -- Additional environment variables for the agent container + env: [] + + # agents.containers.agent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off + # agents.containers.agent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off + ## If not set, fall back to the value of datadog.logLevel. + logLevel: # INFO + + # agents.containers.agent.resources -- Resource requests and limits for the agent container. + resources: + requests: + cpu: 200m + memory: 256Mi + limits: + cpu: 200m + memory: 256Mi + + # agents.containers.agent.healthPort -- Port number to use in the node agent for the healthz endpoint + healthPort: 5555 + + # agents.containers.agent.livenessProbe -- Override default agent liveness probe settings + # @default -- Every 15s / 6 KO / 1 OK + livenessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + successThreshold: 1 + failureThreshold: 6 + + # agents.containers.agent.readinessProbe -- Override default agent readiness probe settings + # @default -- Every 15s / 6 KO / 1 OK + readinessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + successThreshold: 1 + failureThreshold: 6 + + # agents.containers.agent.securityContext -- Allows you to overwrite the default container SecurityContext for the agent container. + securityContext: {} + + processAgent: + # agents.containers.processAgent.env -- Additional environment variables for the process-agent container + env: [] + + # agents.containers.processAgent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off + ## If not set, fall back to the value of datadog.logLevel. + logLevel: # INFO + + # agents.containers.processAgent.resources -- Resource requests and limits for the process-agent container + resources: + requests: + cpu: 100m + memory: 200Mi + limits: + cpu: 100m + memory: 200Mi + + # agents.containers.processAgent.securityContext -- Allows you to overwrite the default container SecurityContext for the process-agent container. + securityContext: {} + + traceAgent: + # agents.containers.traceAgent.env -- Additional environment variables for the trace-agent container + env: + + # agents.containers.traceAgent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off + logLevel: # INFO + + # agents.containers.traceAgent.resources -- Resource requests and limits for the trace-agent container + resources: + requests: + cpu: 50m + memory: 100Mi + limits: + cpu: 50m + memory: 100Mi + + # agents.containers.traceAgent.livenessProbe -- Override default agent liveness probe settings + # @default -- Every 15s + livenessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + + # agents.containers.traceAgent.securityContext -- Allows you to overwrite the default container SecurityContext for the trace-agent container. + securityContext: {} + + systemProbe: + # agents.containers.systemProbe.env -- Additional environment variables for the system-probe container + env: [] + + # agents.containers.systemProbe.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off. + ## If not set, fall back to the value of datadog.logLevel. + logLevel: # INFO + + # agents.containers.systemProbe.resources -- Resource requests and limits for the system-probe container + resources: + requests: + cpu: 50m + memory: 100Mi + limits: + cpu: 50m + memory: 100Mi + + # agents.containers.systemProbe.securityContext -- Allows you to overwrite the default container SecurityContext for the system-probe container. + securityContext: + privileged: true + capabilities: + add: ["SYS_ADMIN", "SYS_RESOURCE", "SYS_PTRACE", "NET_ADMIN", "NET_BROADCAST", "IPC_LOCK"] + securityAgent: + # agents.containers.securityAgent.env -- Additional environment variables for the security-agent container + env: + + # agents.containers.securityAgent.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, and off + ## If not set, fall back to the value of datadog.logLevel. + logLevel: # INFO + + # agents.containers.securityAgent.resources -- Resource requests and limits for the security-agent container + resources: + requests: + cpu: 100m + memory: 200Mi + limits: + cpu: 100m + memory: 200Mi + + initContainers: + # agents.containers.initContainers.resources -- Resource requests and limits for the init containers + resources: {} + # requests: + # cpu: 100m + # memory: 200Mi + # limits: + # cpu: 100m + # memory: 200Mi + + # agents.volumes -- Specify additional volumes to mount in the dd-agent container + volumes: [] + # - hostPath: + # path: + # name: + + # agents.volumeMounts -- Specify additional volumes to mount in all containers of the agent pod + volumeMounts: [] + # - name: + # mountPath: + # readOnly: true + + # agents.useHostNetwork -- Bind ports on the hostNetwork + ## Useful for CNI networking where hostPort might + ## not be supported. The ports need to be available on all hosts. It Can be + ## used for custom metrics instead of a service endpoint. + ## + ## WARNING: Make sure that hosts using this are properly firewalled otherwise + ## metrics and traces are accepted from any host able to connect to this host. + useHostNetwork: false + + # agents.dnsConfig -- specify dns configuration options for datadog cluster agent containers e.g ndots + ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config + dnsConfig: {} + # options: + # - name: ndots + # value: "1" + + # agents.podAnnotations -- Annotations to add to the DaemonSet's Pods + podAnnotations: {} + # : '[{"key": "", "value": ""}]' + + # agents.tolerations -- Allow the DaemonSet to schedule on tainted nodes (requires Kubernetes >= 1.6) + tolerations: + - effect: NoSchedule + operator: Exists + + # agents.nodeSelector -- Allow the DaemonSet to schedule on selected nodes + ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ + nodeSelector: {} + + # agents.affinity -- Allow the DaemonSet to schedule using affinity rules + ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity + affinity: {} + + # agents.updateStrategy -- Allow the DaemonSet to perform a rolling update on helm update + ## ref: https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/ + updateStrategy: + type: RollingUpdate + rollingUpdate: + maxUnavailable: "10%" + + # agents.priorityClassName -- Sets PriorityClassName if defineds + priorityClassName: + + # agents.podLabels -- Sets podLabels if defined + # Note: These labels are also used as label selectors so they are immutable. + podLabels: {} + + # agents.additionalLabels -- Adds labels to the Agent daemonset and pods + additionalLabels: {} + # key: "value" + + # agents.useConfigMap -- Configures a configmap to provide the agent configuration. Use this in combination with the `agents.customAgentConfig` parameter. + useConfigMap: # false + + # agents.customAgentConfig -- Specify custom contents for the datadog agent config (datadog.yaml) + ## ref: https://docs.datadoghq.com/agent/guide/agent-configuration-files/?tab=agentv6 + ## ref: https://github.com/DataDog/datadog-agent/blob/master/pkg/config/config_template.yaml + ## Note the `agents.useConfigMap` needs to be set to `true` for this parameter to be taken into account. + customAgentConfig: + # # Autodiscovery for Kubernetes + # listeners: + # - name: kubelet + # config_providers: + # - name: kubelet + # polling: true + # # needed to support legacy docker label config templates + # - name: docker + # polling: true + # + # Enable APM by setting the DD_APM_ENABLED envvar to true, or override this configuration + apm_config: + enabled: true + apm_non_local_traffic: true + # # Enable java cgroup handling. Only one of those options should be enabled, + # # depending on the agent version you are using along that chart. + # + # # agent version < 6.15 + # # jmx_use_cgroup_memory_limit: true + # + # # agent version >= 6.15 + # # jmx_use_container_support: true + + networkPolicy: + # agents.networkPolicy.create -- If true, create a NetworkPolicy for the agents. + # DEPRECATED. Use datadog.networkPolicy.create instead + create: false + + clusterChecksRunner: + # clusterChecksRunner.enabled -- If true, deploys agent dedicated for running the Cluster Checks instead of running in the Daemonset's agents. + ## ref: https://docs.datadoghq.com/agent/autodiscovery/clusterchecks/ + enabled: false + + ## Define the Datadog image to work with. + image: + # clusterChecksRunner.image.repository -- Datadog Agent image repository to use + ## use "gcr.io/datadoghq/agent" for Datadog Agent 7 + repository: gcr.io/datadoghq/agent + + # clusterChecksRunner.image.tag -- Define the Agent version to use + ## Use 7-jmx to enable jmx fetch collection + # tag: 7.24.1 + + # clusterChecksRunner.image.pullPolicy -- Datadog Agent image pull policy + pullPolicy: IfNotPresent + + # clusterChecksRunner.image.pullSecrets -- Datadog Agent repository pullSecret (ex: specify docker registry credentials) + ## See https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod + pullSecrets: [] + # - name: "" + + # clusterChecksRunner.createPodDisruptionBudget -- Create the pod disruption budget to apply to the cluster checks agents + createPodDisruptionBudget: false + + # Provide Cluster Checks Deployment pods RBAC configuration + rbac: + # clusterChecksRunner.rbac.create -- If true, create & use RBAC resources + create: true + + # clusterChecksRunner.rbac.dedicated -- If true, use a dedicated RBAC resource for the cluster checks agent(s) + dedicated: false + + # clusterChecksRunner.rbac.serviceAccountAnnotations -- Annotations to add to the ServiceAccount if clusterChecksRunner.rbac.dedicated is true + serviceAccountAnnotations: {} + + # clusterChecksRunner.rbac.serviceAccountName -- Specify service account name to use (usually pre-existing, created if create is true) + serviceAccountName: default + + # clusterChecksRunner.replicas -- Number of Cluster Checks Runner instances + ## If you want to deploy the clusterChecks agent in HA, keep at least clusterChecksRunner.replicas set to 2. + ## And increase the clusterChecksRunner.replicas according to the number of Cluster Checks. + replicas: 2 + + # clusterChecksRunner.resources -- Datadog clusterchecks-agent resource requests and limits. + resources: + requests: + cpu: 100m + memory: 200Mi + limits: + cpu: 100m + memory: 200Mi + + # clusterChecksRunner.affinity -- Allow the ClusterChecks Deployment to schedule using affinity rules. + ## By default, ClusterChecks Deployment Pods are forced to run on different Nodes. + ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity + affinity: {} + + # clusterChecksRunner.strategy -- Allow the ClusterChecks deployment to perform a rolling update on helm update + ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy + strategy: + type: RollingUpdate + rollingUpdate: + maxSurge: 1 + maxUnavailable: 0 + + # clusterChecksRunner.dnsConfig -- specify dns configuration options for datadog cluster agent containers e.g ndots + ## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config + dnsConfig: {} + # options: + # - name: ndots + # value: "1" + + # clusterChecksRunner.nodeSelector -- Allow the ClusterChecks Deployment to schedule on selected nodes + ## Ref: https://kubernetes.io/docs/user-guide/node-selection/ + # + nodeSelector: {} + + # clusterChecksRunner.tolerations -- Tolerations for pod assignment + ## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ + # + tolerations: [] + + # clusterChecksRunner.healthPort -- Port number to use in the Cluster Checks Runner for the healthz endpoint + healthPort: 5555 + + # clusterChecksRunner.livenessProbe -- Override default agent liveness probe settings + # @default -- Every 15s / 6 KO / 1 OK + ## In case of issues with the probe, you can disable it with the + ## following values, to allow easier investigating: + # + # livenessProbe: + # exec: + # command: ["/bin/true"] + # + livenessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + successThreshold: 1 + failureThreshold: 6 + + # clusterChecksRunner.readinessProbe -- Override default agent readiness probe settings + # @default -- Every 15s / 6 KO / 1 OK + ## In case of issues with the probe, you can disable it with the + ## following values, to allow easier investigating: + # + # readinessProbe: + # exec: + # command: ["/bin/true"] + # + readinessProbe: + initialDelaySeconds: 15 + periodSeconds: 15 + timeoutSeconds: 5 + successThreshold: 1 + failureThreshold: 6 + + # clusterChecksRunner.podAnnotations -- Annotations to add to the cluster-checks-runner's pod(s) + podAnnotations: {} + # key: "value" + + # clusterChecksRunner.env -- Environment variables specific to Cluster Checks Runner + ## ref: https://github.com/DataDog/datadog-agent/tree/master/Dockerfiles/agent#environment-variables + env: + - name: DD_KUBELET_TLS_VERIFY + value: "false" + + # clusterChecksRunner.volumes -- Specify additional volumes to mount in the cluster checks container + volumes: [] + # - hostPath: + # path: + # name: + + # clusterChecksRunner.volumeMounts -- Specify additional volumes to mount in the cluster checks container + volumeMounts: [] + # - name: + # mountPath: + # readOnly: true + + networkPolicy: + # clusterChecksRunner.networkPolicy.create -- If true, create a NetworkPolicy for the cluster checks runners. + # DEPRECATED. Use datadog.networkPolicy.create instead + create: false + + # clusterChecksRunner.additionalLabels -- Adds labels to the cluster checks runner deployment and pods + additionalLabels: {} + # key: "value" + + # clusterChecksRunner.securityContext -- Allows you to overwrite the default PodSecurityContext on the clusterchecks pods. + securityContext: {} + + datadog-crds: + crds: + # datadog-crds.crds.datadogMetrics -- Set to true to deploy the DatadogMetrics CRD + datadogMetrics: true + + kube-state-metrics: + rbac: + # kube-state-metrics.rbac.create -- If true, create & use RBAC resources + create: true + + serviceAccount: + # kube-state-metrics.serviceAccount.create -- If true, create ServiceAccount, require rbac kube-state-metrics.rbac.create true + create: true + + # kube-state-metrics.serviceAccount.name -- The name of the ServiceAccount to use. + ## If not set and create is true, a name is generated using the fullname template + name: datadog-kube-state-metrics + + # kube-state-metrics.resources -- Resource requests and limits for the kube-state-metrics container. + resources: + requests: + cpu: 100m + memory: 256Mi + limits: + cpu: 100m + memory: 256Mi + + # kube-state-metrics.nodeSelector -- Node selector for KSM. KSM only supports Linux. + nodeSelector: + kubernetes.io/os: linux destination: server: https://192.168.1.2:6443