Venafi Kubernetes Agent Helm values¶

metrics.enabled¶

true

Enable the metrics server.
If false, the metrics server will be disabled, and the other metrics fields below will be ignored.

metrics.podmonitor.enabled¶

false

Create a PodMonitor to add the metrics to Prometheus, if you are using Prometheus Operator.
For more information, see the Prometheus Operator documentation.

metrics.podmonitor.namespace¶

The namespace that the pod monitor should live in.
Defaults to the venafi-kubernetes-agent namespace.

metrics.podmonitor.prometheusInstance¶

default

Specifies the prometheus label on the created PodMonitor.
This is used when different Prometheus instances have label selectors matching different PodMonitors.

metrics.podmonitor.interval¶

60s

The interval to scrape metrics.

metrics.podmonitor.scrapeTimeout¶

30s

The timeout before a metrics scrape fails.

metrics.podmonitor.labels¶

{}

Additional labels to add to the PodMonitor.

metrics.podmonitor.annotations¶

{}

Additional annotations to add to the PodMonitor.

metrics.podmonitor.honorLabels¶

false

Keep labels from scraped data, overriding server-side labels.

metrics.podmonitor.endpointAdditionalProperties¶

{}

EndpointAdditionalProperties allows setting additional properties on the endpoint, such as relabelings, metricRelabelings, etc.

For example:

endpointAdditionalProperties:
 relabelings:
 - action: replace
   sourceLabels:
   - __meta_kubernetes_pod_node_name
   targetLabel: instance

replicaCount¶

1

Default replicas. Do not scale up.

image.repository¶

registry.venafi.cloud/venafi-agent/venafi-agent

Default to Open Source image repository.

image.pullPolicy¶

IfNotPresent

Defaults to only pull if not already present.

imagePullSecrets¶

[]

Specify image pull credentials if using a private registry.
example: - name: my-pull-secret.

nameOverride¶

""

Helm default setting to override release name, usually leave blank.

fullnameOverride¶

""

Helm default setting, use this to shorten the full install name.

serviceAccount.create¶

true

Specifies whether a service account should be created.

serviceAccount.annotations¶

{}

Annotations YAML to add to the service account.

serviceAccount.name¶

""

The name of the service account to use.
If blank and serviceAccount.create is true, a name is generated using the fullname template of the release.

podAnnotations¶

{}

Additional YAML annotations to add the the pod.

podSecurityContext¶

{}

Optional Pod (all containers) SecurityContext options. For more information, see Set the security context for a Pod.

http_proxy¶

Configures the HTTP_PROXY environment variable where a HTTP proxy is required.

https_proxy¶

Configures the HTTPS_PROXY environment variable where a HTTP proxy is required.

no_proxy¶

Configures the NO_PROXY environment variable where a HTTP proxy is required, but certain domains should be excluded.

securityContext.capabilities.drop[0]¶

ALL

securityContext.readOnlyRootFilesystem¶

true

securityContext.runAsNonRoot¶

true

resources.requests.memory¶

200Mi

resources.requests.cpu¶

200m

resources.limits.memory¶

500Mi

nodeSelector¶

{}

Embed YAML for nodeSelector settings. For more information, see Assign Pods to Nodes.

tolerations¶

[]

Embed YAML for toleration settings. For more information, see Taints and Tolerations.

affinity¶

{}

Embed YAML for Node affinity settings. For more information, see Assign Pods using Node Affinity.

command¶

[]

Specify the command to run overriding default binary.

extraArgs¶

[]

Specify additional arguments to pass to the agent binary.
For example ["--strict", "--oneshot"]

volumes¶

[]

Additional volumes to add to the Venafi Kubernetes Agent container. This is
useful for mounting a custom CA bundle. For example:

volumes:
  - name: cabundle
    configMap:
      name: cabundle
      optional: false
      defaultMode: 0644

In order to create the ConfigMap, you can use the following command:

kubectl create configmap cabundle \  
  --from-file=cabundle=./your/custom/ca/bundle.pem

volumeMounts¶

[]

Additional volume mounts to add to the Venafi Kubernetes Agent container.
This is useful for mounting a custom CA bundle. Any PEM certificate mounted under /etc/ssl/certs will be loaded by the Venafi Kubernetes Agent. For

example:

volumeMounts:
  - name: cabundle
    mountPath: /etc/ssl/certs/cabundle
    subPath: cabundle
    readOnly: true

authentication.secretName¶

agent-credentials

Name of the secret containing the private key

authentication.secretKey¶

privatekey.pem

Key name in the referenced secret

Venafi Connection¶

Configure VenafiConnection authentication

authentication.venafiConnection.enabled¶

false

When set to true, the Venafi Kubernetes Agent will authenticate to
Venafi is using the configuration in a VenafiConnection resource. Use venafiConnection.enabled=true for secretless authentication. When set to true, the authentication.secret values will be ignored and the. Secret with authentication.secretName will not be mounted into the Venafi Kubernetes Agent Pod.

authentication.venafiConnection.name¶

venafi-components

The name of a VenafiConnection resource which contains the configuration
for authenticating to Venafi.

authentication.venafiConnection.namespace¶

venafi

The namespace of a VenafiConnection resource which contains the
configuration for authenticating to Venafi.

config.server¶

https://api.venafi.cloud/

API URL of the Venafi Control Plane API. For EU tenants, set this value to https://api.venafi.eu/. If you are using the VenafiConnection authentication method, you must set the API URL using the field spec.vcp.url on the
VenafiConnection resource instead.

config.clientId¶

""

The client-id to be used for authenticating with the Venafi Control Plane. Only useful when using a Key Pair Service Account in the Venafi Control Plane. You can obtain the cliend ID by creating a Key Pair Service Account in the Venafi Control Plane.

config.period¶

0h1m0s

Send data back to the platform every minute unless changed.

config.clusterName¶

""

Name for the cluster resource if it needs to be created in Venafi Control Plane.

config.clusterDescription¶

""

Description for the cluster resource if it needs to be created in Venafi Control Plane.

config.ignoredSecretTypes[0]¶

kubernetes.io/service-account-token

config.ignoredSecretTypes[1]¶

kubernetes.io/dockercfg

config.ignoredSecretTypes[2]¶

kubernetes.io/dockerconfigjson

config.ignoredSecretTypes[3]¶

kubernetes.io/basic-auth

config.ignoredSecretTypes[4]¶

kubernetes.io/ssh-auth

config.ignoredSecretTypes[5]¶

bootstrap.kubernetes.io/token

config.ignoredSecretTypes[6]¶

helm.sh/release.v1

config.configmap.name¶

null

config.configmap.key¶

null

podDisruptionBudget.enabled¶

false

Enable or disable the PodDisruptionBudget resource, which helps prevent downtime
during voluntary disruptions such as a Node upgrade.

CRDs¶

The CRDs installed by this chart are annotated with "helm.sh/resource-policy: keep", this prevents them from being accidentally removed by Helm when this chart is deleted. After deleting the installed chart, the user still has to manually remove the remaining CRDs.

crds.forceRemoveValidationAnnotations¶

false

The 'x-kubernetes-validations' annotation is not supported in Kubernetes 1.22 and below.
This annotation is used by CEL, which is a feature introduced in Kubernetes 1.25 that improves how validation is performed. This option allows to force the 'x-kubernetes-validations' annotation to be excluded, even on Kubernetes 1.25+ clusters.

crds.venafiConnection.include¶

false