Skip to content

Commit

Permalink
Update charts/k8s-monitoring/docs/examples/platforms/openshift/README.md
Browse files Browse the repository at this point in the history 
Co-authored-by: Beverly Buchanan <[email protected]>
  • Loading branch information
@petewall @BeverlyJaneJ
petewall and BeverlyJaneJ authored Jan 2, 2025
1 parent 941cb4d commit 68419ee
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions charts/k8s-monitoring/docs/examples/platforms/openshift/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,16 @@

This example shows the modifications requires to deploy to an OpenShift cluster.

These modifications skip the deployment of kube-state-metrics and Node Exporter, since they will already be present on
the cluster, and adjust the configuration to Grafana Alloy to find those existing components.
It also modifies Grafana Alloy to lock down security and permissions.
These modifications:
- Skip the deployment of kube-state-metrics and Node Exporter, since they are already present on

Check failure on line 10 in charts/k8s-monitoring/docs/examples/platforms/openshift/README.md

View workflow job for this annotation

GitHub Actions / runner / markdownlint 

[markdownlint] reported by reviewdog 🐶
MD030/list-marker-space Spaces after list markers [Expected: 3; Actual: 1]

Raw Output:
charts/k8s-monitoring/docs/examples/platforms/openshift/README.md:10:1 MD030/list-marker-space Spaces after list markers [Expected: 3; Actual: 1]

Check failure on line 10 in charts/k8s-monitoring/docs/examples/platforms/openshift/README.md

View workflow job for this annotation

GitHub Actions / runner / markdownlint 

[markdownlint] reported by reviewdog 🐶
MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Skip the deployment of kube-..."]

Raw Output:
charts/k8s-monitoring/docs/examples/platforms/openshift/README.md:10 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Skip the deployment of kube-..."]
the cluster
- Adjust the configuration to Grafana Alloy to find those existing components

Check failure on line 12 in charts/k8s-monitoring/docs/examples/platforms/openshift/README.md

View workflow job for this annotation

GitHub Actions / runner / markdownlint 

[markdownlint] reported by reviewdog 🐶
MD030/list-marker-space Spaces after list markers [Expected: 3; Actual: 1]

Raw Output:
charts/k8s-monitoring/docs/examples/platforms/openshift/README.md:12:1 MD030/list-marker-space Spaces after list markers [Expected: 3; Actual: 1]
- Make changes to Grafana Alloy to lock down security and permissions

Check failure on line 13 in charts/k8s-monitoring/docs/examples/platforms/openshift/README.md

View workflow job for this annotation

GitHub Actions / runner / markdownlint 

[markdownlint] reported by reviewdog 🐶
MD030/list-marker-space Spaces after list markers [Expected: 3; Actual: 1]

Raw Output:
charts/k8s-monitoring/docs/examples/platforms/openshift/README.md:13:1 MD030/list-marker-space Spaces after list markers [Expected: 3; Actual: 1]

The `platform: openshift` switch also creates SecurityContextConstraints objects that modifies the permissions for the
The `platform: openshift` switch also creates SecurityContextConstraints objects that modifiy the permissions for the
Grafana Alloy.

Note that these alloy pods cannot enable `readOnlyRootFilesystem` because they require being able to write to their
Note that these Alloy pods cannot enable `readOnlyRootFilesystem` because they require being able to write to their
storage path, which defaults to `/tmp/alloy`.

## Values
Expand Down

0 comments on commit 68419ee

Please sign in to comment.