Add blog self-hosted-shoots-on-openstack-gep-28-reaches-a-new-provider

[rfranzke]

Purpose

@tobschli This PR proposes a new blog post titled:

"Self-Hosted Shoots on OpenStack: GEP-28 Reaches a New Provider"

The purpose of the blog post is to inform the community about new Gardener features or changes (2026-08-05).

Notes to Reviewers

This blog post was generated with AI assistance from the source material listed below.
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.

Source Material

• https://youtu.be/X07luCqDtno?t=1359
• https://gardener.cloud/community/review-meetings/2026-reviews/
• [GEP-28] Always enable SSH for Self hosted Shoots gardener#15270
• [GEP-28] Fixes for managed scenario gardener#15369
• Implement GetMachineStatus machine-controller-manager-provider-openstack#405
• [GEP-36] SelfHostedShootExposure gardener-extension-provider-openstack#1401

Instructions for Reviewers

❌ If the blog post isn't viable

• Close this PR
• Delete the branch

✏️ If the blog post 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-08-05-self-hosted-shoots-on-openstack-gep-28-reaches-a-new-provider

3. Review the content in website/blog/2026/08/08-05-self-hosted-shoots-on-openstack-gep-28-reaches-a-new-provider.md.
4. Make any necessary edits, additions, or removals, and then push the changes:

git add website/blog/2026/08/08-05-self-hosted-shoots-on-openstack-gep-28-reaches-a-new-provider.md
git commit --amend --no-edit
git push origin +blog/2026-08-05-self-hosted-shoots-on-openstack-gep-28-reaches-a-new-provider

✅ If the blog post is ready

• 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.

@tobschli Thank you for contributing to the Gardener blog!

[netlify]

✅ Deploy Preview for gardener-docs ready!

Name	Link
🔨 Latest commit	0c2fb15
🔍 Latest deploy log	https://app.netlify.com/projects/gardener-docs/deploys/6a745014b0651c00087408e6
😎 Deploy Preview	https://deploy-preview-1040--gardener-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[gardener-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign klocke-io for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Warning

Review limit reached

@BoHristova, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 914bf68d-c54b-4896-871a-aa2025848849

📥 Commits

Reviewing files that changed from the base of the PR and between 43b7d39 and 0c2fb15.

📒 Files selected for processing (2)

• hugo/content/blog/2026/08/08-05-self-hosted-shoots-on-openstack-gep-28-reaches-a-new-provider.md
• hugo/content/blog/2026/08/_index.md

---

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.}

[tobschli]

/lgtm

[gardener-prow]

@tobschli: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[BoHristova]

@tobschli, @rfranzke, I had to move the blog post to hugo/content/, since website/ doesn't exist anymore (see #1025).