feat: migrate Loki to community Monolithic chart - #2
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
18.13.1SingleBinarytoMonolithiclonghorn-standardwith explicit PVC retention on delete/scale-downValidation / upstream review
The migration follows Grafana's current Monolithic Helm guidance: one replica requires
commonConfig.replication_factor: 1, the community chart usesdeploymentMode: Monolithic, and the chart still deploys theloki-gatewayservice used by Alloy. The release pin is the publishedloki-18.13.1chart.Filesystem storage is intentional for this sanitized small-cluster reference and is documented as non-HA. External object storage remains the recommendation for larger/HA Loki deployments.
Follow-up before merge
Render the exact chart with the committed values and verify the gateway service/PVC fields. The temporary README noreply-test marker should also be removed before merge.