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

Implement Status for MultiClusterService #460

Closed
wahabmk opened this issue Oct 8, 2024 · 0 comments · Fixed by #550
Closed

Implement Status for MultiClusterService #460

wahabmk opened this issue Oct 8, 2024 · 0 comments · Fixed by #550
Assignees

Comments

@wahabmk
Copy link
Contributor

wahabmk commented Oct 8, 2024

Incorporates #361.

  • 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.
@wahabmk wahabmk moved this from Todo to In Progress in Project 2A Oct 24, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Project 2A Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant