chore(kumactl): upgrade grafana/loki to 3.3.2 in observability manifests #12639
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.
Motivation
I know we plan to remove
kumactl install observability
eventually, but I think we should update its components for now, especially if it’s easy to do. Once the versions are more current, Renovate can take care of updates going forward.Implementation information
Upgraded
grafana/loki
from 2.5.0 to 3.3.2 in the Kubernetes manifest used bykumactl install observability
. Updatedloki.yaml
to match the new configuration format after following migration steps from 2.6.0 to 3.3.0. Tested locally to ensure everything works as expected.Supporting documentation
Related to: #11693
loki.yaml
before (base64 decoded)loki.yaml
after all migrations (base64 decoded)