Add blog extensible-advertised-addresses-for-shoots#744
Conversation
gardener-robot
added
needs/review
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
|
@gardener-ci-robot Command |
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
gardener-robot
added
the
lifecycle/stale
|
@dnaeon Do you want to merge this PR? If not, please close it. |
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle rotten |
gardener-prow
bot
added
lifecycle/rotten
I somehow missed the first notifications about this one. Looks good from my side. /lgtm |
|
@dnaeon: 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. |
|
/approve |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
gardener-prow
bot
added
the
approved
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 0ba405f809791d34c2df49bc74568edc7a3fec24 |
📝 WalkthroughWalkthroughA new blog post documenting an enhancement to Gardener's Shoot endpoint discovery mechanism, enabling Ingress resources in control-plane namespaces to be advertised via a label-based opt-in mechanism that extends status.advertisedAddresses with generated naming patterns. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
gardener-prow
bot
added
size/M
gardener-github-actions
bot
added
the
ok-to-test
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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/2025/10/10-22-extensible-advertised-addresses-for-shoots.md`:
- Line 16: Change the heading "The Challenge of Endpoint Discovery" from an h3
to an h2 to follow sequential markdown heading levels; locate the line
containing "### The Challenge of Endpoint Discovery" in the file and replace the
leading "###" with "##" so the document title (h1) is followed by this h2.
- Line 20: The heading "A New Standard for Advertising Endpoints" is currently
an h3 (###) causing an MD001 heading-increment violation; change it to h2 (##)
so the document follows proper heading order. Locate the heading line in the
blog post and replace the leading "###" with "##" (ensure surrounding headings
remain consistent), then run the markdown linter to confirm the MD001 error is
resolved.
- Line 48: The "Future Enhancements" heading currently uses an h3 ("### Future
Enhancements") which violates MD001; update that heading to h2 by replacing "###
Future Enhancements" with "## Future Enhancements" in the blog post (look for
the exact string "Future Enhancements") so the heading level increments
correctly relative to surrounding content.
- Line 52: The "Find Out More" heading currently uses an h3 ("### Find Out
More") causing an MD001 heading-increment violation; change that heading to h2
("## Find Out More") so it follows the previous section level and resolves the
markdown heading level issue, updating the line that contains the exact heading
text "Find Out More".
|
|
||
| Gardener has introduced a new feature that enhances the discoverability of services running within a Shoot's control plane. While the `.status.advertisedAddresses` field in the `Shoot` resource has always provided key endpoints like the API server URL, it now supports extension by other components. | ||
|
|
||
| ### The Challenge of Endpoint Discovery |
There was a problem hiding this comment.
Fix heading level to follow markdown best practices.
The heading jumps from h1 (document title) to h3, skipping h2. Markdown best practices require incrementing heading levels by one at a time.
📝 Proposed fix for heading level
-### The Challenge of Endpoint Discovery
+## The Challenge of Endpoint DiscoveryAs per static analysis hints, this addresses the MD001 (heading-increment) violation.
📝 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.
| ### The Challenge of Endpoint Discovery | |
| ## The Challenge of Endpoint Discovery |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 16-16: 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/2025/10/10-22-extensible-advertised-addresses-for-shoots.md` at
line 16, Change the heading "The Challenge of Endpoint Discovery" from an h3 to
an h2 to follow sequential markdown heading levels; locate the line containing
"### The Challenge of Endpoint Discovery" in the file and replace the leading
"###" with "##" so the document title (h1) is followed by this h2.
|
|
||
| Previously, only a default set of addresses, such as the internal and external API server URLs and the service account issuer URL, were published in a Shoot's status. Endpoints for other essential services deployed in the control plane—like Plutono, Prometheus, or Vali—remained hidden. Discovering these required direct access to the Seed cluster and knowledge of the Shoot's technical ID, making them inaccessible to end-users and external tooling that only interact with the `Shoot` resource. | ||
|
|
||
| ### A New Standard for Advertising Endpoints |
There was a problem hiding this comment.
Fix heading level to follow markdown best practices.
This heading also uses h3 instead of h2, creating the same heading-increment violation.
📝 Proposed fix for heading level
-### A New Standard for Advertising Endpoints
+## A New Standard for Advertising EndpointsAs per static analysis hints, this addresses the MD001 (heading-increment) violation.
📝 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 Standard for Advertising Endpoints | |
| ## A New Standard for Advertising Endpoints |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@website/blog/2025/10/10-22-extensible-advertised-addresses-for-shoots.md` at
line 20, The heading "A New Standard for Advertising Endpoints" is currently an
h3 (###) causing an MD001 heading-increment violation; change it to h2 (##) so
the document follows proper heading order. Locate the heading line in the blog
post and replace the leading "###" with "##" (ensure surrounding headings remain
consistent), then run the markdown linter to confirm the MD001 error is
resolved.
|
|
||
| This mechanism provides a standardized way for any component, including custom extensions, to publish its endpoints directly on the `Shoot` object, making them programmatically discoverable for users and automation. | ||
|
|
||
| ### Future Enhancements |
There was a problem hiding this comment.
Fix heading level to follow markdown best practices.
This heading also uses h3 instead of h2.
📝 Proposed fix for heading level
-### Future Enhancements
+## Future EnhancementsAs per static analysis hints, this addresses the MD001 (heading-increment) violation.
📝 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.
| ### Future Enhancements | |
| ## Future Enhancements |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@website/blog/2025/10/10-22-extensible-advertised-addresses-for-shoots.md` at
line 48, The "Future Enhancements" heading currently uses an h3 ("### Future
Enhancements") which violates MD001; update that heading to h2 by replacing "###
Future Enhancements" with "## Future Enhancements" in the blog post (look for
the exact string "Future Enhancements") so the heading level increments
correctly relative to surrounding content.
|
|
||
| This feature currently supports `Ingress` resources, with plans to include support for `Gateway` resources from the Kubernetes Gateway API in the future. | ||
|
|
||
| ### Find Out More |
There was a problem hiding this comment.
Fix heading level to follow markdown best practices.
This heading also uses h3 instead of h2.
📝 Proposed fix for heading level
-### Find Out More
+## Find Out MoreAs per static analysis hints, this addresses the MD001 (heading-increment) violation.
📝 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.
| ### Find Out More | |
| ## Find Out More |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@website/blog/2025/10/10-22-extensible-advertised-addresses-for-shoots.md` at
line 52, The "Find Out More" heading currently uses an h3 ("### Find Out More")
causing an MD001 heading-increment violation; change that heading to h2 ("##
Find Out More") so it follows the previous section level and resolves the
markdown heading level issue, updating the line that contains the exact heading
text "Find Out More".
5 participants
Purpose
@dnaeon This is an automatically generated draft pull request proposing a new blog post based on your Gardener review meeting presentation you gave on 2025-10-22 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/2025-10-22-extensible-advertised-addresses-for-shootswebsite/blog/2025/10/10-22-extensible-advertised-addresses-for-shoots.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.
@dnaeon Thank you for helping us share valuable updates from the Gardener project with the community!
Summary by CodeRabbit
Release Notes