Skip to content

docs: Update user-guides/recover_ingester_pods_in_zone_failure_outages.md #18309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ydFu
Copy link
Contributor

@ydFu ydFu commented Jul 2, 2025

What this PR does / why we need it:
The following is the corrected, working YAML configuration that conforms to the Loki Operator’s CRD (Custom Resource Definition) structure

Which issue(s) this PR fixes:
none

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • 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.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

Signed-off-by: Ader Fu <ader.ydfu@gmail.com>
Copy link
Collaborator

@xperimental xperimental left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for spotting this issue 👍

Just a minor change...

Comment on lines 39 to 40
- version: v12
effectiveDate: "2022-06-01"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We usually do not indent lists in our YAML examples:

Suggested change
- version: v12
effectiveDate: "2022-06-01"
- version: v12
effectiveDate: "2022-06-01"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment on lines 48 to 49
- topologyKey: topology.kubernetes.io/zone
maxSkew: 1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- topologyKey: topology.kubernetes.io/zone
maxSkew: 1
- topologyKey: topology.kubernetes.io/zone
maxSkew: 1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion, I hadn't thought about such details in the yaml format before.

Signed-off-by: Ader Fu <ader.ydfu@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants