Skip to content
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

Clarify the importance of DNS pods scheduling on infra nodes #125956

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

aasserzo
Copy link
Contributor

This change aims to clarify the importance of scheduling DNS pods on infrastructure nodes, due to MDSD being unable to deliver logs from nodes where DNS pods are not running.

Copy link
Contributor

@aasserzo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 3b38479:

✅ Validation status: passed

File Status Preview URL Details
articles/openshift/howto-infrastructure-nodes.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@johnmarco

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Feb 27, 2025
@johnmarco
Copy link
Contributor

#sign-off

@v-dirichards v-dirichards merged commit b673726 into MicrosoftDocs:main Feb 27, 2025
2 checks passed
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