[KEP-31]: Adding ControllerRevision support to the RoleBasedGroup#27
[KEP-31]: Adding ControllerRevision support to the RoleBasedGroup#27cheyang merged 3 commits intosgl-project:mainfrom
Conversation
7bd3142 to
ba9745c
Compare
Signed-off-by: 柏存 <[email protected]>
ba9745c to
536d807
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a KEP (Kubernetes Enhancement Proposal) for adding ControllerRevision support to the RoleBasedGroup (RBG) object, enabling historical state tracking and version awareness for RBG configurations.
Key Changes:
- Proposes using Kubernetes ControllerRevision resources to store historical RBG states
- Introduces per-role revision tracking to prevent unintended cross-role updates
- Maintains backward compatibility with existing semantic equality-based update mechanisms
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| keps/31-rbg-controller-revision/kep.yaml | Metadata file defining the KEP proposal including authorship, status, and milestone information |
| keps/31-rbg-controller-revision/README.md | Detailed KEP documentation explaining motivation, design, API changes, and implementation approach for ControllerRevision support |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: bcfre <[email protected]>
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Ⅰ. Motivation
KEP: adding ControllerRevision support to the RoleBasedGroup (RBG) object to store its historical states.
Ⅱ. Modifications
kep proposal
Ⅲ. Does this pull request fix one issue?
fixes #21
Ⅳ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅴ. Describe how to verify it
VI. Special notes for reviews
Checklist
make fmt.