Add blog fine-tune-your-shoot-control-plane-placement-with-zone-awareness

[gardener-answering-machine]

Purpose

@rfranzke This is an automatically generated draft pull request proposing a new blog post based on your Gardener review meeting presentation you gave on 2026-04-01 titled:

"Fine-Tune Your Shoot Control Plane Placement with Zone Awareness"

The purpose of the blog post is to actively inform the community about new Gardener features or changes, as discussed during review meetings.

Notes to Reviewers

This draft was automatically generated by LLMs using the review meeting recording and referenced materials.
Please evaluate whether this topic is suitable for a blog post. If so, review and edit the content as needed.
If you decide the topic isn't appropriate for a blog post, feel free to close this PR and delete the branch.

⚠️ This is an experimental GenAI feature. Feedback is welcome! Please direct it to @vlerenc. Thank you!

Instructions for Reviewers

❌ If the draft isn't viable

• Close this PR
• Delete the branch

✏️ If the draft is viable but requires editing

1. Clone the repository and change to the directory:

git clone https://github.com/gardener/documentation
cd documentation

2. Check out the branch:

git fetch origin && git checkout blog/2026-04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness

3. Review the content in website/blog/2026/04/04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness.md.
4. Make any necessary edits, additions, or removals, and then push the changes:

git add website/blog/2026/04/04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness.md
git commit --amend --no-edit
git push origin +blog/2026-04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness

✅ If the draft is ready for review

• Mark this PR as Ready for review
• Invite additional reviewers (optional step)
• Comment with /lgtm to approve (required step)

The documentation team will review your PR, as required by branch protection.
They will merge it once you (and any additional reviewers) have approved it.

@rfranzke Thank you for helping us share valuable updates from the Gardener project with the community!

Summary by CodeRabbit

• Documentation
  • Added blog post introducing zone-aware control plane placement feature, covering zone selection modes and their application scenarios for different cluster types on multi-zone infrastructure to optimize latency and costs.

[netlify]

✅ Deploy Preview for gardener-docs ready!

Name	Link
🔨 Latest commit	5a42174
🔍 Latest deploy log	https://app.netlify.com/projects/gardener-docs/deploys/69cd0e24f17830000865f800
😎 Deploy Preview	https://deploy-preview-918--gardener-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 70 (🟢 up 5 from production) Accessibility: 97 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 90 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new blog post documenting Gardener's zone-aware control plane placement feature for Shoot resources on multi-zone Seeds has been added. The feature introduces spec.settings.zoneSelection with Prefer and Enforce modes to optimize availability zone selection. Additionally, a blog index file for April 2026 has been created.

Changes

Cohort / File(s)	Summary
Blog Content website/blog/2026/04/04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness.md, website/blog/2026/04/_index.md	Added blog post documenting zone-aware Shoot control plane placement feature, including Prefer and Enforce selection modes, applicability conditions, and implementation details. Created blog index for April aggregation and listing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

kind/enhancement, needs/review

Suggested reviewers

• n-boshnakov

Poem

🐰 Hops through zones with glee,
Control planes placed so perfectly,
No more latency woes to bear,
Zone-aware scheduling, beyond compare! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete against the template. It lacks the required '/kind' categorization (marked as TODO) and 'Which issue(s) this PR fixes' section, though it provides context about the PR's purpose.	Complete the description template by selecting an appropriate '/kind' identifier (likely 'task' or 'enhancement') and add or clarify which issue this PR addresses.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a blog post about zone-aware Shoot control plane placement, which matches the file additions and content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch blog/2026-04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness

---

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

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

[rfranzke]

/kind enhancement

[rfranzke]

/lgtm
/approve

[gardener-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rfranzke

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rfranzke]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gardener-prow]

LGTM label has been added.

Details

Git tree hash: a87f33b4fdccace071a03d67ee3812b814207422

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@website/blog/2026/04/_index.md`:
- Line 3: Frontmatter references a nonexistent layout "blog-list"; either remove
the line layout: blog-list from the post or import and register the BlogIndex
component (BlogIndex.vue) as a layout named "blog-list" in the theme's layout
registration (the theme entry where layouts are imported/exported) so the layout
key matches a registered layout.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 74a801f4-d12b-46b7-89ad-f414c1dcb1fd

📥 Commits

Reviewing files that changed from the base of the PR and between e432c4e and 5a42174.

📒 Files selected for processing (2)

• website/blog/2026/04/04-01-fine-tune-your-shoot-control-plane-placement-with-zone-awareness.md
• website/blog/2026/04/_index.md

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify whether the frontmatter layout key "blog-list" is registered in theme config.
# Expected: a layout map entry like `Layout`/`layouts` containing `blog-list` (or an equivalent resolver).

rg -n -C3 --iglob '*.ts' --iglob '*.js' --iglob '*.vue' 'blog-list|BlogIndex|layout[s]?\s*[:=]'

Repository: gardener/documentation

Length of output: 1142

---

🏁 Script executed:

#!/bin/bash
# Search for VitePress theme configuration and layout definitions
# Look in .vitepress directory for config and theme files

# List .vitepress structure
find .vitepress -type f -name '*.ts' -o -name '*.js' -o -name '*.json' 2>/dev/null | head -20

echo "---"

# Search for explicit layout configuration or mapping
rg -n 'layouts|BlogIndex|blog-list' .vitepress/ --type ts --type js --type vue 2>/dev/null || true

Repository: gardener/documentation

Length of output: 296

---

🏁 Script executed:

#!/bin/bash
# Check the main theme index file for layout configuration
cat -n .vitepress/theme/index.ts

Repository: gardener/documentation

Length of output: 1047

---

🏁 Script executed:

#!/bin/bash
# Check for layouts directory and BlogList component
find .vitepress/theme -type d -name 'layouts' 2>/dev/null

# Search for any BlogList component
rg -l 'BlogList|blog-list' .vitepress/theme/components/ 2>/dev/null || echo "No matches in components"

# List all files in theme/components to see what's available
echo "---"
ls -1 .vitepress/theme/components/

Repository: gardener/documentation

Length of output: 292

---

🏁 Script executed:

#!/bin/bash
# Final check: verify blog-list is NOT referenced anywhere in theme or config
rg 'blog-list' .vitepress/ 2>/dev/null || echo "No references to 'blog-list' in .vitepress"

# Check if BlogIndex is used anywhere or exported from theme
rg 'BlogIndex' .vitepress/theme/index.ts 2>/dev/null || echo "BlogIndex not in theme index"

Repository: gardener/documentation

Length of output: 279

---

layout: blog-list is not registered in the theme and will cause rendering to fail.

The layout key blog-list is referenced in frontmatter but does not exist in the VitePress theme configuration. BlogIndex.vue exists as a component with a .blog-list CSS class, but it is not imported or registered in .vitepress/theme/index.ts. Either remove the layout: blog-list line or register BlogIndex as a layout in the theme.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@website/blog/2026/04/_index.md` at line 3, Frontmatter references a
nonexistent layout "blog-list"; either remove the line layout: blog-list from
the post or import and register the BlogIndex component (BlogIndex.vue) as a
layout named "blog-list" in the theme's layout registration (the theme entry
where layouts are imported/exported) so the layout key matches a registered
layout.