Skip to main content
logoTetrate Patch ServiceVersion: alpha

Agent Helm Values v0.1.0

These are the values of the patch-service-agent-helm chart from version v0.1.0 to v0.2.1. Agents of these versions find workloads by label rather than from the release catalog, and report only when a workload changes; upgrade to v0.4.0 or later to stop labeling workloads.

Agent-only installs

On the managed data plane, Tetrate keeps the agent current through upgrade pull requests, so these versions only remain on agent-only installs.

Each value is marked with who owns it: Yours, Set by onboarding, or Leave as is. Where to Set Values explains each, and how to change a value on your kind of install.

Discovery​

What the agent watches and which workloads it reports. Before chart v0.4.0 the agent has no release catalog: it reports every container of the Deployments and DaemonSets that selector matches, in the namespaces podNamespaces lists.

ValueOwnerDescriptionDefault
podNamespacesYoursNamespaces the agent watches for Deployments and DaemonSets. Empty watches every namespace. It narrows what the agent looks at, not its permissions.[]
selectorSet by onboardingA Kubernetes label selector that opts Deployments and DaemonSets into reporting, matched against their own labels. The agent reports every container of the workloads it matches. Onboarding sets it to dataplane.tetrate.io=<customer-id>, so a workload is reported only once it carries that label; on the managed data plane Tetrate also excludes app=redis. Empty reports every workload in the watched namespaces, including your own applications.""

Connection to the Patch Service​

How the agent identifies its cluster and reaches the Patch Service. All of them are set by onboarding.

ValueOwnerDescriptionDefault
customerIdSet by onboardingYour organization's identifier. Every report is filed under it. Required when server.url is set.""
clusterNameLeave as isThe cluster's name, written into the chart. Onboarding sets clusterNameConfigMap instead, because the name is only settled when the cluster registers. One of the two is required.""
clusterNameConfigMap.nameSet by onboardingA ConfigMap in the agent's namespace to read the cluster name from. Onboarding creates patch-service-agent-config and sets this to it. Takes precedence over clusterName.""
clusterNameConfigMap.keySet by onboardingThe key in that ConfigMap holding the name.clusterName
server.urlSet by onboardingThe Patch Service API the agent reports to. Empty makes the agent log what it finds instead of reporting it, which is only useful to try the chart out.""
server.tokenUrlSet by onboardingWhere the agent obtains its access tokens.https://auth.patch.tetrate.io/oauth2/token
server.clientIdSet by onboardingThe agent's machine identity for your organization.""
server.existingSecretNameSet by onboardingA Secret holding the client secret for server.clientId. Onboarding creates patch-service-agent and sets this to it, so the secret never appears in the Helm release.""
server.existingSecretKeySet by onboardingThe key in that Secret holding the client secret.clientSecret
server.clientSecretLeave as isThe client secret given directly as a value. The chart then creates a Secret for it, and the secret is stored in the Helm release history. Use server.existingSecretName instead.""

Image​

ValueOwnerDescriptionDefault
image.repositorySet by onboardingWhere the agent image is pulled from. Onboarding sets fips-containers.teg.tetratelabs.com/patch-service-agent, which your Tetrate Hub credentials can pull. On an agent-only install, change it only if you mirror the agent image into your own registry.ghcr.io/tetrateio/patch-service-agent
image.tagSet by onboardingThe agent version. Onboarding pins it, so an upgrade has to set it: see Upgrading the Agent.the chart's version
image.pullPolicyYours, agent-onlyStandard Kubernetes image pull policy. On the managed data plane Tetrate sets it to Always.IfNotPresent
imagePullSecretsSet by onboardingSecrets used to pull the image. Onboarding sets tetrate-pull-credentials, which holds your Tetrate Hub credentials. If you mirror the agent image, add the Secret for your registry.[]

Availability and Scheduling​

Standard Kubernetes settings for the agent's Deployment.

ValueOwnerDescriptionDefault
replicaCountYoursNumber of agent replicas. Only one reports at a time; the others stand by to take over. More than one requires leaderElection: true.1
leaderElectionLeave as isCoordinates replicas through a Lease in the agent's namespace, so only one reports. Leave it enabled; the chart refuses replicaCount above 1 without it.true
resourcesYoursCPU and memory requests and limits for the agent container.{}
nodeSelectorYoursNode labels the agent's Pods must run on.{}
tolerationsYoursTolerations for the agent's Pods, to run on tainted nodes.[]
affinityYoursAffinity and anti-affinity rules for the agent's Pods.{}
podAnnotationsYoursAnnotations added to the agent's Pods.{}
podLabelsSet by onboardingLabels added to the agent's Pods. Onboarding adds dataplane.tetrate.io: <customer-id>. Add your own labels alongside it on either kind of install: they are kept, and only that one label is Tetrate's.{}
commonLabelsSet by onboardingLabels added to every resource the chart creates. Onboarding adds dataplane.tetrate.io: <customer-id>. Add your own labels alongside it on either kind of install: they are kept, and only that one label is Tetrate's.{}
envYours, agent-onlyExtra environment variables for the agent container, as standard Kubernetes EnvVar entries. Use it for LOG_LEVEL (debug, info, error, or none; default info). On the managed data plane Tetrate sets this list, so your entries are replaced.[]

Resource Names and Service Account​

ValueOwnerDescriptionDefault
nameOverrideLeave as isThe name used in resource names and the app.kubernetes.io/name label.agent
fullnameOverrideLeave as isReplaces the full resource name prefix. The onboarding flows find the agent by its resource names, so changing either name makes the Patch Service treat the agent as one it did not install.""
serviceAccount.createLeave as isCreates the agent's service account.true
serviceAccount.nameLeave as isThe service account's name. Empty derives it from the release.""
serviceAccount.annotationsYoursAnnotations on the service account.{}

Values the Chart Rejects​

The chart fails the install, with a message naming the problem, instead of installing an agent that cannot work:

  • Neither clusterName nor clusterNameConfigMap.name is set.
  • server.url is set without customerId, server.tokenUrl, server.clientId, or a client secret through server.existingSecretName or server.clientSecret.
  • replicaCount is above 1 with leaderElection: false.

Next Steps​

  • Agent Helm Values explains where to set these values on your kind of install, and which page matches the chart version you run.
  • Upgrade the agent on an agent-only install, keeping the values you set.