chore: add docs for wiring in pre-reqs for S3/MetalLB #1235
Conversation
| overrides: | ||
| loki: |
There was a problem hiding this comment.
We should also add the overrides to lock down the egress traffic to strictly what is necessary here (uds-loki-config chart has some values for storage egress that when not specified default to egress anywhere).
| overrides: | ||
| velero: |
There was a problem hiding this comment.
Same comment here on the egress policy overrides, see the values here.
| :::caution | ||
| If you are using the in-cluster Minio Operator UDS Package for backups you must ensure that the volumes that back that storage are themselves backed up! Cluster or deployment issues may result in a loss of Minio as well as the application you intend to back up. | ||
| ::: |
There was a problem hiding this comment.
nit, but I wonder if there's a better place to put this caution note given that it applies to both Loki and Velero (and is currently "nested" under the Velero section). We could just copy/paste it to Loki but that doesn't feel right 😅
| loki: | ||
| values: |
There was a problem hiding this comment.
nit: this confused me initially (especially when comparing against the minio example) - can we add the boilerplate of overrides, package, component, etc?
| velero: | ||
| values: |
There was a problem hiding this comment.
Same comment as loki on adding the boilerplate to the example.
Description
Adds some docs for S3 pre-reqs and mentions the MetalLB package
Related Issue
Fixes #N/A
Type of change
Steps to Validate
Checklist before merging