Tetrate Patch ServiceVersion: alphaAgent 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 versions | Reference |
|---|---|
v0.4.4 and later | Agent Helm Values v0.4.4 |
v0.4.0 to v0.4.3 | Agent Helm Values v0.4.0 |
v0.3.1 to v0.3.2 | Agent Helm Values v0.3.1 |
v0.1.0 to v0.2.1 | Agent Helm Values v0.1.0 |
The CHART column of helm list -n tetrate-dataplane-system shows the version an agent-only install runs, as patch-service-agent-helm-<version>. On the managed data plane, it is charts.patch-service-agent.version in agent/values-versions.yaml in your repository.
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.
| Install | Where values live | How to change them |
|---|---|---|
Agent only: tetrate onboard, the Manual connection steps, or a cloud account install | The patch-service-agent Helm release in tetrate-dataplane-system | Save them with helm get values, edit the file, and helm upgrade with it. Upgrading the Agent walks through the commands. |
| Managed data plane | agent/values-customer.yaml, and agent/envs/<environment>/values-customer.yaml for one environment, in your GitOps repository | Open a pull request, as described in Working with Your Repository. Never use helm against a managed agent: ArgoCD reverts it. |
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-only install, keep the value
helm get valuesshows. On the managed data plane, Tetrate sets it after your customer files are applied, so a value you set for it invalues-customer.yamlhas no effect. - Leave as is: changing it is supported by the chart, but no Patch Service install expects it to change.
Next Steps
- Agent Helm Values v0.4.4 for the values of the current agent.
- Upgrade the agent on an agent-only install, keeping the values you set.
- Name your registry mirror with
releaseCatalog.registryAliases, the value new clusters most often need.