Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(chart): rename doc ref of controller.securityContext to agent.securityContext #5808

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions operations/helm/charts/grafana-agent/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ internal API changes are not present.
Unreleased
----------

### Other changes

- Update `container.securityContext` Helm value reference to renamed `agent.securityContext`. (@hainenber)

0.28.0 (2023-11-21)
-------------------

Expand Down
8 changes: 4 additions & 4 deletions operations/helm/charts/grafana-agent/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,9 +168,9 @@ used. When provided, `agent.configMap.content` must hold a valid River configura

[default-config]: ./config/example.river

### controller.securityContext
### agent.securityContext

`controller.securityContext` sets the securityContext passed to the Grafana
`agent.securityContext` sets the securityContext passed to the Grafana
Agent container.

By default, Grafana Agent containers are not able to collect telemetry from the
Expand Down Expand Up @@ -241,7 +241,7 @@ This capability is disabled by default.
To expose logs from other containers to Grafana Agent:

* Set `agent.mounts.dockercontainers` to `true`.
* Set `controller.securityContext` to:
* Set `agent.securityContext` to:
```yaml
privileged: true
runAsUser: 0
Expand All @@ -256,7 +256,7 @@ To expose this information to Grafana Agent for telemetry collection:

* Set `agent.mounts.dockercontainers` to `true`.
* Mount `/proc` and `/sys` from the host into the container.
* Set `controller.securityContext` to:
* Set `agent.securityContext` to:
```yaml
privileged: true
runAsUser: 0
Expand Down
8 changes: 4 additions & 4 deletions operations/helm/charts/grafana-agent/README.md.gotmpl
Original file line number Diff line number Diff line change
Expand Up @@ -80,9 +80,9 @@ used. When provided, `agent.configMap.content` must hold a valid River configura

[default-config]: ./config/example.river

### controller.securityContext
### agent.securityContext

`controller.securityContext` sets the securityContext passed to the Grafana
`agent.securityContext` sets the securityContext passed to the Grafana
Agent container.

By default, Grafana Agent containers are not able to collect telemetry from the
Expand Down Expand Up @@ -153,7 +153,7 @@ This capability is disabled by default.
To expose logs from other containers to Grafana Agent:

* Set `agent.mounts.dockercontainers` to `true`.
* Set `controller.securityContext` to:
* Set `agent.securityContext` to:
```yaml
privileged: true
runAsUser: 0
Expand All @@ -168,7 +168,7 @@ To expose this information to Grafana Agent for telemetry collection:

* Set `agent.mounts.dockercontainers` to `true`.
* Mount `/proc` and `/sys` from the host into the container.
* Set `controller.securityContext` to:
* Set `agent.securityContext` to:
```yaml
privileged: true
runAsUser: 0
Expand Down