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

Adopting a Standardized ClusterInventory API from SIG Multi-Cluster #247

Open
qiujian16 opened this issue Aug 4, 2023 · 4 comments
Open
Labels
enhancement New feature or request

Comments

@qiujian16
Copy link
Member

Describe the enhancement
OCM today uses ManagedCluster to represent a cluster under management. There is an on-going discussion in the sig-multicluster to build a common cluster inventory api https://docs.google.com/document/d/1sUWbe81BTclQ4Uax3flnCoKtEWngH-JA9MyCqljJCBM/edit. It would bring many benefits to OCM to adopt this API since the integration with consumers of cluster inventory API would be much easier.

To adopt it once the sig-multicluster reaches the agreement on the cluster inventory API. We should:

  • sync between ManagedCluster and cluster inventory API which ensures backward compatibility.
  • placement scheduling should consume cluster inventory API also.
  • work with sig-multicluster to enhance the API and investigate if we are able to fully replace ManagedCluster with it in the long term
@qiujian16 qiujian16 added the enhancement New feature or request label Aug 4, 2023
@qiujian16
Copy link
Member Author

cc @mikeshng

Copy link

github-actions bot commented Dec 3, 2023

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@github-actions github-actions bot added the Stale label Dec 3, 2023
@qiujian16 qiujian16 removed the Stale label Dec 4, 2023
Copy link

github-actions bot commented Apr 2, 2024

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

Copy link

github-actions bot commented Aug 1, 2024

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

2 participants