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

Replace Fleet Cluster Nodes Ready column #10542

Closed
richard-cox opened this issue Mar 1, 2024 · 9 comments · Fixed by #11041
Closed

Replace Fleet Cluster Nodes Ready column #10542

richard-cox opened this issue Mar 1, 2024 · 9 comments · Fixed by #11041
Assignees
Labels
area/fleet kind/enhancement QA/manual-test Indicates issue requires manually testing
Milestone

Comments

@richard-cox
Copy link
Member

richard-cox commented Mar 1, 2024

@kkaempf
Copy link

kkaempf commented Apr 17, 2024

@nwmac @gaktive Fleet would need this for v2.9.0 already 🥺

@gaktive gaktive modified the milestones: v2.10.0, v2.9.0 Apr 17, 2024
@gaktive
Copy link
Member

gaktive commented Apr 17, 2024

@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?

@thehejik
Copy link

@gaktive Just letting know that QA is done, please see report rancher/fleet#1973 (comment) with details.

@sbulage
Copy link

sbulage commented May 2, 2024

@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.

@nwmac nwmac added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label May 3, 2024
@aalves08 aalves08 self-assigned this May 16, 2024
@yonasberhe23
Copy link
Contributor

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?

@yonasberhe23 yonasberhe23 added QA/manual-test Indicates issue requires manually testing and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels May 24, 2024
@thehejik
Copy link

thehejik commented May 31, 2024

This seems to be fixed. This is how it looks currently in 2.9-e833f80f53b04b301f881f96154392c34d3b56b1-head with fleet 104.0.0+up0.10.0-rc.14:
image

The Bundles Ready counter seems to be valid. There is always one Bundle for fleet-agent* and another Bundle for my added GitRepo resource (which is also shown) so two in total.

@manno
Copy link
Member

manno commented Jun 14, 2024

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.

@nwmac
Copy link
Member

nwmac commented Jun 14, 2024

Thanks @manno - if you could create a new issue, that would be great.

@nwmac
Copy link
Member

nwmac commented Jun 14, 2024

@yonasberhe23 I think this can be marked done now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fleet kind/enhancement QA/manual-test Indicates issue requires manually testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants