Add blog say-goodbye-to-provider-extensions-introducing-the-new-remote-setup#903
Conversation
gardener-prow
bot
added
the
do-not-merge/work-in-progress
✅ Deploy Preview for gardener-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughA new blog post is added documenting the migration from provider-extensions to a remote setup architecture based on gardener-operator. The post includes setup instructions, architecture comparison, automation details, and future enhancement plans. Changes
Suggested labels
Suggested reviewers
Poem
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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. Comment Tip CodeRabbit can approve the review once all CodeRabbit's comments are resolved.Enable the |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
gardener-prow
bot
added
do-not-merge/needs-kind
gardener-prow
bot
removed
the
do-not-merge/work-in-progress
|
/kind enhancement |
|
@oliver-goetz: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this:
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. |
gardener-prow
bot
removed
the
do-not-merge/needs-kind
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md`:
- Line 9: Replace the escaped byte sequence in the author name string ("name:
\"Oliver G\xF6tz\"") with the proper UTF-8 character so it reads "Oliver Götz";
update the value used for the author name field (the quoted name string) and
ensure the file is saved in UTF-8 encoding so markdown renders the character
correctly.
- Line 15: Change the main content heading "A New, Fully Remote Architecture"
from level 3 (###) to level 2 (##) so it directly follows the title; scan the
rest of this markdown (e.g., other top-level section headings) and adjust any
other main section headings using ### to ## to maintain proper hierarchical
increments by one level.
- Line 29: The link in the blog text points to a non-existent
docs/deployment/getting_started_remotely.md; update the markdown to either
replace that URL with a valid existing doc (for example
docs/deployment/getting_started_locally.md or docs/deployment/setup_gardener.md)
or add the missing getting_started_remotely.md file in the gardener docs and
ensure the link target matches its path; locate the reference by searching for
the "make remote-up" line or the "Deploying Gardener Remotely" anchor in the
blog post and update the href accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1d28b78b-9ada-4499-862f-227428b0b2fc
📒 Files selected for processing (1)
website/blog/2026/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md
| authors: | ||
| - avatar: https://avatars.githubusercontent.com/oliver-goetz | ||
| login: oliver-goetz | ||
| name: "Oliver G\xF6tz" |
There was a problem hiding this comment.
Fix character encoding for author name.
The author name uses escape sequence \xF6 instead of the proper UTF-8 character. This may cause rendering issues in some markdown processors.
✏️ Proposed fix
- name: "Oliver G\xF6tz"
+ name: "Oliver Götz"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| name: "Oliver G\xF6tz" | |
| name: "Oliver Götz" |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@website/blog/2026/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md`
at line 9, Replace the escaped byte sequence in the author name string ("name:
\"Oliver G\xF6tz\"") with the proper UTF-8 character so it reads "Oliver Götz";
update the value used for the author name field (the quoted name string) and
ensure the file is saved in UTF-8 encoding so markdown renders the character
correctly.
|
|
||
| The Gardener team is excited to announce a significant overhaul of the development setup for working with provider extensions. The former `provider-extensions` setup, which relied on a deprecated Helm chart, has been completely replaced by a new, streamlined `remote` setup based on `gardener-operator`. | ||
|
|
||
| ### A New, Fully Remote Architecture |
There was a problem hiding this comment.
Fix heading level to follow markdown hierarchy.
The heading uses level 3 (###) but should use level 2 (##) as the first content heading after the title. This violates markdown best practices for heading hierarchy. As per static analysis, heading levels should only increment by one level at a time.
📝 Proposed fix for this and other main section headings
-### A New, Fully Remote Architecture
+## A New, Fully Remote ArchitectureApply the same fix to other main section headings:
-### Getting Started with the `remote` Setup
+## Getting Started with the `remote` Setup-### Future Enhancements
+## Future Enhancements-### A Breaking Change for a Better Experience
+## A Breaking Change for a Better Experience-### Further Reading
+## Further Reading📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### A New, Fully Remote Architecture | |
| ## A New, Fully Remote Architecture |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 15-15: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@website/blog/2026/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md`
at line 15, Change the main content heading "A New, Fully Remote Architecture"
from level 3 (###) to level 2 (##) so it directly follows the title; scan the
rest of this markdown (e.g., other top-level section headings) and adjust any
other main section headings using ### to ## to maintain proper hierarchical
increments by one level.
...te/blog/2026/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md
Show resolved
Hide resolved
|
Bozhidara Hristova left a comment: The navigation label for March is generated differently from the others. @n-boshnakov Do you have an idea why this might be happening? Browser metadata |
n-boshnakov
left a comment
n-boshnakov
left a comment
There was a problem hiding this comment.
Some minor changes to take care of.
|
|
||
| The Gardener team is excited to announce a significant overhaul of the development setup for working with provider extensions. The former `provider-extensions` setup, which relied on a deprecated Helm chart, has been completely replaced by a new, streamlined `remote` setup based on `gardener-operator`. | ||
|
|
||
| ### A New, Fully Remote Architecture |
There was a problem hiding this comment.
| ### A New, Fully Remote Architecture | |
| ## A New, Fully Remote Architecture |
| * **Increased Stability:** Developers can keep their setup running on the remote cluster without worrying about breaking a local `kind` cluster or impacting their local machine's resources. | ||
| * **Improved Reliability:** The new architecture eliminates previous workarounds, like the SSH tunnel, resulting in a more robust and reliable development environment. | ||
|
|
||
| ### Getting Started with the `remote` Setup |
There was a problem hiding this comment.
| ### Getting Started with the `remote` Setup | |
| ## Getting Started with the `remote` Setup |
...te/blog/2026/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md
Show resolved
Hide resolved
|
|
||
| Getting started is now centered around the `make remote-up` command and the configuration files located in directories containing `remote` within `./dev-setup/`. The process is detailed in the new [Deploying Gardener Remotely](https://github.com/gardener/gardener/blob/master/docs/deployment/getting_started_remotely.md) documentation. | ||
|
|
||
| On the first run, the setup automatically generates necessary YAML files from templates. If you use a Gardener Shoot cluster as your remote cluster, many configuration steps—like setting up networking, regions, and provider types—are automated by pulling information from the shoot's `shoot-info` ConfigMap. |
There was a problem hiding this comment.
| On the first run, the setup automatically generates necessary YAML files from templates. If you use a Gardener Shoot cluster as your remote cluster, many configuration steps—like setting up networking, regions, and provider types—are automated by pulling information from the shoot's `shoot-info` ConfigMap. | |
| On the first run, the setup automatically generates the necessary YAML files from templates. If you use a Gardener Shoot cluster as your remote cluster, many configuration steps—like setting up networking, regions, and provider types—are automated by pulling information from the shoot's `shoot-info` ConfigMap. |
|
|
||
| On the first run, the setup automatically generates necessary YAML files from templates. If you use a Gardener Shoot cluster as your remote cluster, many configuration steps—like setting up networking, regions, and provider types—are automated by pulling information from the shoot's `shoot-info` ConfigMap. | ||
|
|
||
| ### Future Enhancements |
There was a problem hiding this comment.
| ### Future Enhancements | |
| ## Future Enhancements |
|
|
||
| Currently, the `remote` setup supports a single soil cluster. However, work is underway to enable the creation of multiple seeds, including managed seeds across different providers, within a single remote setup. This will be further simplified by upcoming native support for image pull secrets in Gardener, which will remove the need for certain workarounds. | ||
|
|
||
| ### A Breaking Change for a Better Experience |
There was a problem hiding this comment.
| ### A Breaking Change for a Better Experience | |
| ## A Breaking Change for a Better Experience |
|
|
||
| ### A Breaking Change for a Better Experience | ||
|
|
||
| It's important to note that this is a **breaking change**. The `provider-extensions` setup has been removed, and there is no direct migration path to the new `remote` setup. If you have an existing setup, you must check out a previous Gardener version (v1.137.0 or earlier) to properly delete it and remove all resources from your infrastructure before adopting the new `remote` setup. |
There was a problem hiding this comment.
| It's important to note that this is a **breaking change**. The `provider-extensions` setup has been removed, and there is no direct migration path to the new `remote` setup. If you have an existing setup, you must check out a previous Gardener version (v1.137.0 or earlier) to properly delete it and remove all resources from your infrastructure before adopting the new `remote` setup. | |
| It is important to note that this is a **breaking change**. The `provider-extensions` setup has been removed, and there is no direct migration path to the new `remote` setup. If you have an existing setup, you must check out a previous Gardener version (v1.137.0 or earlier) to properly delete it and remove all resources from your infrastructure before adopting the new `remote` setup. |
|
|
||
| *** | ||
|
|
||
| ### Further Reading |
There was a problem hiding this comment.
| ### Further Reading | |
| ## Further Reading |
3 participants
Purpose
@oliver-goetz This is an automatically generated draft pull request proposing a new blog post based on your Gardener review meeting presentation you gave on 2026-03-18 titled:
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.
Instructions for Reviewers
❌ If the draft isn't viable
✏️ If the draft is viable but requires editing
git clone https://github.com/gardener/documentation cd documentationgit fetch origin && git checkout blog/2026-03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setupwebsite/blog/2026/03/03-18-say-goodbye-to-provider-extensions-introducing-the-new-remote-setup.md.✅ If the draft is ready for review
/lgtmto 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.
@oliver-goetz Thank you for helping us share valuable updates from the Gardener project with the community!
Summary by CodeRabbit