-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
member cluster webhook setup #24
Labels
kind/enhancement
New feature or request
Comments
Wenfeng-GAO
added a commit
that referenced
this issue
Jan 19, 2024
16 tasks
Wenfeng-GAO
added a commit
that referenced
this issue
Jan 19, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Jan 30, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Feb 1, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Feb 1, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Feb 1, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Feb 1, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Feb 1, 2024
Wenfeng-GAO
added a commit
that referenced
this issue
Feb 1, 2024
zoumo
pushed a commit
that referenced
this issue
Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
I'd like to propose the implementation of a member cluster webhook feature for the Rollout project. This webhook would introduce two key capabilities that can aid in platform presentation and observability, as well as grant more control to the rollout process during updates.
Motivation
As the Rollout project aims to streamline and manage the deployment process in Kubernetes environments efficiently, having additional observability and control during the rollout process can significantly benefit users who wish to have more granular insights and management options. The proposed member cluster webhook would serve this purpose with the following functionalities:
Batch Labeling for Updated Pods: During the rolling update process, it would be beneficial to tag updated pods with labels indicating their batch group. This labeling can help in tracking which pods have been upgraded and to which batch they belong, effectively aiding platform display features and providing valuable information for observability purposes.
Deployment Pause Before Upgrade: To enable the Rollout controller to take over the upgrade process seamlessly, there should be a capability to pause the Deployment before it begins updating. This pause function would allow the Rollout controller to intercede and manage the deployment according to the defined strategy and parameters.
Desired Capabilities
Pod Labeling During Rolling Updates:
Control Over Deployment Updates:
The text was updated successfully, but these errors were encountered: