Skip to content
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

Introduce a Lazy Activation feature to Policy #4563

Open
2 of 3 tasks
chaosi-zju opened this issue Jan 19, 2024 · 2 comments
Open
2 of 3 tasks

Introduce a Lazy Activation feature to Policy #4563

chaosi-zju opened this issue Jan 19, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@chaosi-zju
Copy link
Member

chaosi-zju commented Jan 19, 2024

What would you like to be added:

Introduced a ActivationPreference filed to Policy, indicating how the referencing resource template will be propagated, in case of policy changes.

If empty, the resource template will respond to policy changes immediately, in other words, any policy changes will drive the resource template to be propagated immediately as per the current propagation rules.

If the value is Lazy means the policy changes will not take effect for now but defer to the resource template changes, in other words, the resource template will not be propagated as per the current propagation rules until there is an update on it.

Why is this needed:

In the scenario where Policy responsibilities are separated from Resource responsibilities, one role is dedicated to Policy management, which is referred to as cluster administrator, and the other role is dedicated to Resource management, which is referred to as user. The cluster administrator would preconfigure some Policies for users, then the users apply their own Resources and propagated them according to the preconfigured Policy.

However, the administrator has requests to modify the Policy in the future, such as migrating propagation clusters. As the current Policy modification is effective immediately, the modification will affect the propagation status of a large number of resource templates and have a great impact on the system.

The administrator is worried that the modification will lead to the failure of the business application in the non-change window, so the administrator hopes that the modification of Policy can be delayed until the business application change window takes effect.

Notes

This feature has some system constraints and risks, which will be described in detail proposal document.


Related Actions

  1. Proposal
  2. Implemention
  3. Test
@chaosi-zju chaosi-zju added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 19, 2024
@chaosi-zju
Copy link
Member Author

CC @RainbowMango

#4564 and #4570 are all PRs about code modification, and ready to review, thanks.

@XiShanYongYe-Chang
Copy link
Member

Can this issue be closed first? The E2E task can be tracked by #4607. @chaosi-zju

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: No status
Development

No branches or pull requests

2 participants