Skip to main content
logoTetrate Patch ServiceVersion: alpha

Agent Helm Values

The agent is installed from the patch-service-agent-helm chart. The values the chart accepts change only in some releases, so the reference has one page for each version that changed them. Use the page for the chart version you run:

Chart versionsReference
v0.5.0 and laterAgent Helm Values v0.5.0
v0.4.4Agent Helm Values v0.4.4
v0.4.0 to v0.4.3Agent Helm Values v0.4.0
v0.3.1 to v0.3.2Agent Helm Values v0.3.1
v0.1.0 to v0.2.1Agent Helm Values v0.1.0

The CHART column of helm list -n tetrate-dataplane-system, or the namespace you installed the agent into, shows the version an agent-only install runs, as patch-service-agent-helm-<version>. When the agent is deployed from your repository, it is the chart version in its deploy file under .tetrate/patch-service-agent/envs/<environment>/: the Argo CD Application's targetRevision, the Flux OCIRepository's tag, or chart-version.json for Terraform.

To read the values of any chart version straight from the chart:

helm show values oci://fips-containers.teg.tetratelabs.com/patch-service-agent-helm --version <chart version>

The registry is private: run helm registry login fips-containers.teg.tetratelabs.com first, or pass --registry-config as described in Upgrading the Agent.

Where to Set Values​

How you change a value depends on how the agent was installed. Either way, start from the values the agent already runs with: the onboarding flows set several values that connect the agent to your organization, and an install that leaves them out stops reporting.

InstallWhere values liveHow to change them
Agent only: tetrate onboard, the Manual connection steps, or a cloud account installThe patch-service-agent Helm release in tetrate-dataplane-system, or the namespace you chose when connectingSave them with helm get values, edit the file, and helm upgrade with it. Upgrading the Agent walks through the commands. The watched namespaces, releaseCatalog.registryAliases, and releaseCatalog.extraRepositories can also be chosen when connecting, as described in Configuring the Agent.
Deployed from your GitOps repository.tetrate/patch-service-agent/values-customer.yaml in the repository, and in a provisioned repository also .tetrate/patch-service-agent/envs/<environment>/values-customer.yaml for one environmentChange the file and commit it the way you change anything in the repository; in a provisioned repository, open a pull request as described in Working with a Provisioned Repository. Never use helm against it: your deploy tool reverts the change.

Each value on the reference pages is marked with who owns it:

  • Yours: safe to change on either kind of install.
  • Set by onboarding: the onboarding flows set it to connect the agent to your organization. On an agent installed with Helm, keep the value helm get values shows. On an agent deployed from your repository, the console filled it in for your account in values-customer.yaml, or Tetrate in values-tetrate.yaml in a provisioned repository: keep it as it is.
  • Leave as is: changing it is supported by the chart, but no Patch Service install expects it to change.

Next Steps​