loki
loki copied to clipboard
docs: Deploy Loki Helm on AWS guide
This is the successor PR to the SSD PR #14327 After an internal discussion, it was decided to focus deployment guides for helm on either Monolithic or distributed (microservice mode). The Loki team felt more comfortable supporting both of these deployment styles since its closer to what we deploy internally.
This PR is part of a large redesign to improve the helm documentation of Loki.
Checklist
- [x] Reviewed the
CONTRIBUTING.md
guide (required) - [x] Documentation added
- [ ] Tests updated
- [x] Title matches the required conventional commits format, see here
-
Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such,
feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
-
Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such,
- [ ] Changes that require user attention or interaction to upgrade are documented in
docs/sources/setup/upgrade/_index.md
- [ ] For Helm chart changes bump the Helm chart version in
production/helm/loki/Chart.yaml
and updateproduction/helm/loki/CHANGELOG.md
andproduction/helm/loki/README.md
. Example PR - [ ] If the change is deprecating or removing a configuration option, update the
deprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR