Add blog introducing-automated-credential-rotation#822
Conversation
gardener-prow
Bot
added
do-not-merge/work-in-progress
ghost
added
the
reviewed/ok-to-test
|
ping @AleksandarSavchev |
gardener-prow
Bot
removed
the
do-not-merge/work-in-progress
|
/lgtm |
|
@AleksandarSavchev: 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. |
📝 WalkthroughWalkthroughA new blog post was added to document the Automated Credential Rotation feature for Gardener. The post explains the feature's configuration through Shoot manifest specifications, default rotation periods, and provides usage examples with YAML snippets. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 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)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Comment |
|
/lgtm |
ghost
added
the
ok-to-test
gardener-prow
Bot
added
kind/enhancement
|
LGTM label has been added. DetailsGit tree hash: 0a0ad5ad1b16c8ee063a2f22273d655e99cb80d9 |
gardener-prow
Bot
added
the
approved
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
website/blog/2026/01/01-28-introducing-automated-credential-rotation.md (1)
51-51: Consider adding details about manual rotation.The statement mentions that "manual rotation via annotations remains available" but doesn't specify which annotations to use or link to documentation. Consider adding a brief example or linking to the manual rotation documentation to help readers who need this feature.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@website/blog/2026/01/01-28-introducing-automated-credential-rotation.md` at line 51, The sentence referencing manual rotation is too vague; update the paragraph that mentions `rotationPeriod` and "manual rotation via annotations" to include the exact annotation key(s) and a short example (e.g., annotation name and value) or add a link to the manual-rotation documentation page; reference the same `rotationPeriod` wording and the phrase "manual rotation via annotations" so readers can find the example quickly.
🤖 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/01/01-28-introducing-automated-credential-rotation.md`:
- Line 15: The post uses h3 headings for top-level sections; change the heading
"Enhanced Security, Effortlessly" from ### to ## and update the other top-level
section headings in this post (the two other section titles currently using ###)
to ## as well so heading hierarchy follows the h1 title and remains consistent
and accessible.
---
Nitpick comments:
In `@website/blog/2026/01/01-28-introducing-automated-credential-rotation.md`:
- Line 51: The sentence referencing manual rotation is too vague; update the
paragraph that mentions `rotationPeriod` and "manual rotation via annotations"
to include the exact annotation key(s) and a short example (e.g., annotation
name and value) or add a link to the manual-rotation documentation page;
reference the same `rotationPeriod` wording and the phrase "manual rotation via
annotations" so readers can find the example quickly.
|
|
||
| Maintaining a strong security posture is crucial for any Kubernetes environment. A key aspect of this is the regular rotation of credentials. To simplify this essential task and reduce operational overhead, Gardener now supports the automatic rotation of several critical credentials during a `Shoot` cluster's maintenance window. | ||
|
|
||
| ### Enhanced Security, Effortlessly |
There was a problem hiding this comment.
Fix heading hierarchy.
The first heading in the post should be h2 (##) rather than h3 (###) to follow proper heading level progression after the h1 title. This improves document structure and accessibility.
📝 Proposed fix
-### Enhanced Security, Effortlessly
+## Enhanced Security, EffortlesslyApply the same change to the other section headings (lines 25 and 55) to maintain consistency:
-### How to Enable Automatic Rotation
+## How to Enable Automatic Rotation-### 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.
| ### Enhanced Security, Effortlessly | |
| ## Enhanced Security, Effortlessly |
🧰 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/01/01-28-introducing-automated-credential-rotation.md` at
line 15, The post uses h3 headings for top-level sections; change the heading
"Enhanced Security, Effortlessly" from ### to ## and update the other top-level
section headings in this post (the two other section titles currently using ###)
to ## as well so heading hierarchy follows the h1 title and remains consistent
and accessible.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: n-boshnakov, 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 |
n-boshnakov
deleted the
blog/2026-01-28-introducing-automated-credential-rotation
branch
4 participants
Purpose
@AleksandarSavchev This is an automatically generated draft pull request proposing a new blog post based on your Gardener review meeting presentation you gave on 2026-01-28 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-01-28-introducing-automated-credential-rotationwebsite/blog/2026/01/01-28-introducing-automated-credential-rotation.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.
@AleksandarSavchev Thank you for helping us share valuable updates from the Gardener project with the community!
Summary by CodeRabbit
Release Notes