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

[Summer OSPP 2024] Karmada supports the OverridePolicy dynamic configuration mechanism. #5608

Closed
7 tasks done
chaunceyjiang opened this issue Sep 26, 2024 · 3 comments
Closed
7 tasks done
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@chaunceyjiang
Copy link
Member

chaunceyjiang commented Sep 26, 2024

What would you like to be added:
Karmada utilizes the Kubernetes native API and provides advanced scheduling capabilities. When scheduling cloud-native applications to different member clusters, users may need to configure some differences for the various member clusters, such as setting different environment variables or images for different member clusters. To address this, Karmada provides a differentiated configuration policy API - OverridePolicy, which can set some differentiated configuration information for different clusters.

Currently, the use of OverridePolicy has a limitation - it can only set some static values and cannot dynamically set values based on certain conditions. This limitation restricts the usage scenarios of OverridePolicy. Therefore, we hope to provide a mechanism that can dynamically set values based on conditions. This will enhance the flexibility of using OverridePolicy for cluster differentiation configuration and bring more extensibility to users. For example, users can extend OverridePolicy by defining CEL or Lua languages, and the community has already tracked related issues to push forward with a specific solution.

See #4739 #4799

As we discussed at the community meeting(2024-08-27), we agree to postpone this feature for a while until there is more evidence showing that this is a common requirement.

So we decided to first implement the more common requirements. See #5330

Project link: https://summer-ospp.ac.cn/org/prodetail/245c40337

Parts of: #4879

Desired outcomes:

@chaunceyjiang chaunceyjiang added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 26, 2024
@sophiefeifeifeiya
Copy link
Contributor

/assign

@RainbowMango
Copy link
Member

/close
All tasks done. Great thanks to @sophiefeifeifeiya @chaunceyjiang

@karmada-bot
Copy link
Collaborator

@RainbowMango: Closing this issue.

In response to this:

/close
All tasks done. Great thanks to @sophiefeifeifeiya @chaunceyjiang

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.

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: Planned In Release 1.12
Development

No branches or pull requests

4 participants