Support a central Flux installation with application status information from the leaf clusters
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
As an Application Owner, I want to see the status of my running applications in the GitLab UI when they are deployed from a central Flux installation to leaf clusters.
As a Platform Engineer, I want to manage a single Flux installation that deploys to multiple clusters and still provide resource status integration in the GitLab UI.
The cluster UI in its current form assumes that Flux and agentk run in the same cluster. Only a single agentk connection can be selected for an environment, and that connection reads the Flux state and the overall cluster resource states too. If Flux deploys its workloads to a leaf cluster, the Flux resource is not deployed to the leaf cluster, thus the Flux reconciliation status is not available in the leaf cluster.
Proposal
Current workaround
The user needs to register two environments:
- one environment tracks the Flux reconciliation status
- one environment reads the overall cluster state for the selected resources
Agentk needs to be installed into both clusters.
Dummy Flux status
Add a (likely) CR to the leaf cluster that mirrors the Flux reconciliation status in the leaf cluster. Show its value in the UI under the Flux reconciliation status.
Agentk supports leaf clusters
Make it possible for agentk to connect to leaf clusters from the Flux control plane cluster, and proxy the cluster state from the leaf clusters to the GitLab UI.
Intended users
Feature Usage Metrics
Does this feature require an audit event?
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.