[networking] Configuring per-node DNS on ACP clusters with NodeNetworkConfigurationPolicy

[jing2uo]

新增一篇 ACP KB 文章。

[coderabbitai]

Warning

Rate limit exceeded

@jing2uo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 11 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a8997e6b-1084-43d5-a524-691736423d8f

📥 Commits

Reviewing files that changed from the base of the PR and between 5c78e3d and 7973209.

📒 Files selected for processing (1)

• docs/en/solutions/Change_a_Nodes_DNS_Servers_and_etcresolvconf_Options_via_NMState_NodeNetworkConfigurationPolicy.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kb/2026-02/change-a-nodes-dns-servers-and-etcresolv

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 37 minutes and 11 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}