You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Clusternet is using a self-defined CRD ManagedCluster to declare a cluster, including cluster ID, labels, access point, status, etc. This CRD is used for cluster managements and multiple cluster scheduling.
While this kind of cluster definitions can be seen and needed in multiple projects. They have much in common, but they are not interactable. It makes harder for Clusternet itself to be compatible with other Kubernetes tools and services, such as Argo, Flux, etc. Also other projects are not easy to directly integrate with Clusternet via a common and standardized API.
Once sig multi-cluster has reached an agreement on below ClusterInventory API, Clusternet would like to adopt and migrate to it.
apiVersion: multicluster.x-k8s.io/v1alpha1kind: ClusterInventorymetadata:
name: some-clusterspec:
accessObjectRefs: # optional object points to the resource that declares how to access the cluster
- group: someGroupresource: someResourcename: someNamenamespace: someNamespacetype: KUBECONFIGtaints:
- key: key1value: value1effect: NoScheduleaddTime: xxxhealthinessProbe:
heartbeatIntervalSeconds: 60status:
version:
kubernetes: 1.26.1resources: # total resources of a clustercapacity:
cpu: 12memory: 12Giallocatable:
cpu: 10memory: 16Giproperties:
- name: clusterset.k8s.iovalue: some-clustersetconditions:
- type: Healthystatus: TruelastTransitionTime: "2023-05-08T07:58:55Z"message: ""
Since this ClusterInventory API has much in common with our current ManagedCluster, there won't be too many inconsistencies with current working flows in Clusternet.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
kind/feature
Why is this needed:
Currently Clusternet is using a self-defined CRD ManagedCluster to declare a cluster, including cluster ID, labels, access point, status, etc. This CRD is used for cluster managements and multiple cluster scheduling.
While this kind of cluster definitions can be seen and needed in multiple projects. They have much in common, but they are not interactable. It makes harder for Clusternet itself to be compatible with other Kubernetes tools and services, such as Argo, Flux, etc. Also other projects are not easy to directly integrate with Clusternet via a common and standardized API.
Once sig multi-cluster has reached an agreement on below
ClusterInventory API
, Clusternet would like to adopt and migrate to it.Since this ClusterInventory API has much in common with our current
ManagedCluster
, there won't be too many inconsistencies with current working flows in Clusternet.The text was updated successfully, but these errors were encountered: