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
We are using Sveltos to deploy services under the hood. So we would need to get the status from Sveltos objects (take a look at ClusterProfile, ClusterSummary and ClusterConfiguration objects).
Sveltos uses custom status objects whereas HMC is using list of metav1.Condition in ManagedCluster.
The reason why I mention ManagedCluster is because it is better to share whatever status is implemented for MultiClusterService with ManagedCluster as one uses Sveltos ClusterProfile and the other uses Sveltos Profile. Sveltos uses ClusterSummary for both these types. Additionally, the ClusterConfiguration object gives a summary of what is deployed on a particular cluster irrespective of how many ClusterProfile or Profile objects are managing deployments on that cluster.
So it makes sense for HMC ManagedCluster and MultiClusterService to share the same status object.
The text was updated successfully, but these errors were encountered:
Incorporates #361.
ClusterProfile
,ClusterSummary
andClusterConfiguration
objects).ManagedCluster
.ManagedCluster
is because it is better to share whatever status is implemented forMultiClusterService
withManagedCluster
as one uses SveltosClusterProfile
and the other uses SveltosProfile
. Sveltos usesClusterSummary
for both these types. Additionally, theClusterConfiguration
object gives a summary of what is deployed on a particular cluster irrespective of how manyClusterProfile
orProfile
objects are managing deployments on that cluster.ManagedCluster
andMultiClusterService
to share the same status object.The text was updated successfully, but these errors were encountered: