-
Notifications
You must be signed in to change notification settings - Fork 268
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
Replace Fleet Cluster Nodes Ready
column
#10542
Comments
@kkaempf ok, we'll have to assess this. I see rancher/fleet#1973 is in QA; are there any other tickets that we need to refer to? |
@gaktive Just letting know that QA is done, please see report rancher/fleet#1973 (comment) with details. |
@richard-cox This is also impacting the imported cluster in the fleet-default workspace too. Currently blocking the existing issue checking... till this fix it, any workaround there, please let us know 😄 thanks in advance. |
I think it would be a good idea to test this manually to make sure the data loads properly and table formatting/data alignment is good. cc @izaac FYI i'm currently working on this area of fleet so we'll have e2e tests for this soon. This code hasn't been merged yet so I'll move this back to review. once merged can you move this to 'To Test' please @aalves08? |
Users often create cluster groups instead of matching clusters by name, however those groups only support a label matcher. Would it be possible to add the user’s labels as a column? Also, I think the bundle count is for all bundles and not limited to the selected namespace. For fleet-default, it will always be actual bundles+1, because of the agent bundle in fleet-local. As discussed, I'll open a new issue. |
Thanks @manno - if you could create a new issue, that would be great. |
@yonasberhe23 I think this can be marked done now |
fleet.cattle.io.cluster
status.agent.readyNodes
andstatus.display.sampleNode
are soon to be removednodeInfo
property, which is used to displayNodes Ready
column in the fleet cluster listreadyBundles
in https://fleet.rancher.io/ref-crds#clusterdisplaylastSeen
in https://fleet.rancher.io/ref-crds#agentstatusThe text was updated successfully, but these errors were encountered: