Update example docs #1023
Open
Update example docs #1023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Pete Wall <[email protected]>
Comment on lines
+7
to
+17
| 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. | ||
|
|
||
| The `platform: openshift` switch also creates SecurityContextConstraints objects that modifies the permissions for the | ||
| Grafana Alloy. | ||
|
|
||
| Note that these alloy pods cannot enable `readOnlyRootFilesystem` because they require being able to write to their | ||
| storage path, which defaults to `/tmp/alloy`. |
There was a problem hiding this comment.
Suggested change
| 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. | |
| The `platform: openshift` switch also creates SecurityContextConstraints objects that modifies the permissions for the | |
| Grafana Alloy. | |
| Note that these alloy pods cannot enable `readOnlyRootFilesystem` because they require being able to write to their | |
| storage path, which defaults to `/tmp/alloy`. | |
| 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 are already present on | |
| the cluster | |
| - Adjust the configuration to Grafana Alloy to find those existing components | |
| - Make changes to Grafana Alloy to lock down security and permissions | |
| 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 | |
| storage path, which defaults to `/tmp/alloy`. |
BeverlyJaneJ
approved these changes
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the
description.txtfiles create the information in the README.md files.