Workload Cluster Operator - GitOps Deployment Feedback & Observability

Problem Statement

When deploying workload clusters via GitOps using the SylvaWorkloadCluster operator, users face a significant observability gap: the operator exposes only a single top-level Ready condition and a flat list of managed resource statuses. Troubleshooting a stuck or failing cluster requires navigating across multiple namespaces, CRDs(SylvaWorkloadCluster → SylvaUnitsRelease → HelmRelease → CAPI MachineDeployment / ControlPlane), and Flux objects - all requiring admin management-cluster access that workload teams typically do not have.

There is no safe, read-only mechanism for workload teams to observe the full deployment status of their clusters,understand the cause of failures, or receive actionable error messages without involving the platform administration team.

Description

The project focuses on simplifying workload cluster deployment observability.

Project Details

Leader: Orange (Priya Goyal)

List of people/organization interested to join:

Related repositories: * workload-cluster-operator * sylva-units-operator * sylvactl

Hackathon Objectives

  • Enrich SylvaWorkloadCluster status conditions aggregating CAPI and Flux resource states.
  • Implement sylvactl workload-cluster status with read-only RBAC and correlated output.
  • Define and validate the minimal read-only RBAC profile (ClusterRole/RoleBinding).
  • Test the feedback loop end-to-end on a live management cluster.