-
Notifications
You must be signed in to change notification settings - Fork 94
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
Comments
cc @mikeshng |
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 |
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 |
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 |
/close |
@qiujian16: Closing this issue. In response to this:
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. |
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:
The text was updated successfully, but these errors were encountered: