I worked on ks console recently. The following pic shows two Flux Applications.
test-kus is a Kustomization type app that has two underlying Kustomization, one of them are ready.
test-fluxcd-helm is a HelmRelease type app that has one ready underlying HelmRelease.
Here's something I want to discuss.
1. The StatusCard
Argocd provide health status but not Fluxcd. (in the red box)
Fluxcd provide Ready Type condition not Synced, OutOfSynced in Argocd.
We can use new ReadyStatus Card instead SyncStatus Card. But I am not sure about the HealthStatus Card.
2. The Table
The Table has name | appType | Source | ReadyNumber colums already.
The UpdateTime is not Suitable because FluxCD Application is Multi-Clusters Application.
So I think this field can be the lastAppliedRevision or something? For example lastAppliedRevision: master/4b8497c in Kustomization or lastAppliedRevision: 0.1.0+1 in HelmRelease.
All discussions and suggestions are welcome.
/kind design
I worked on ks console recently. The following pic shows two Flux Applications.
test-kus
is a Kustomization type app that has two underlying Kustomization, one of them are ready.test-fluxcd-helm
is a HelmRelease type app that has one ready underlying HelmRelease.Here's something I want to discuss.
1. The StatusCard
Argocd provide health status but not Fluxcd. (in the red box) Fluxcd provide Ready Type condition not Synced, OutOfSynced in Argocd. We can use new ReadyStatus Card instead SyncStatus Card. But I am not sure about the HealthStatus Card.
2. The Table
The Table has name | appType | Source | ReadyNumber colums already. The UpdateTime is not Suitable because FluxCD Application is Multi-Clusters Application. So I think this field can be the lastAppliedRevision or something? For example
lastAppliedRevision: master/4b8497c
in Kustomization orlastAppliedRevision: 0.1.0+1
in HelmRelease.All discussions and suggestions are welcome. /kind design