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

Aspirational: Create view(s) more appropriate to manage large scale k8s operations #11285

Open
aalves08 opened this issue Jun 21, 2024 · 2 comments
Labels
area/extensions kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@aalves08
Copy link
Member

aalves08 commented Jun 21, 2024

Large scale k8s operations might face some challenges with managing their k8s infrastructures. Thinking of Edge devices is a scenario where we might have thousands of clusters of devices.

Could we provide, at least, a better overview in those cases? How would that interface would look like? Create an extension or more to customise the UI to those particular usecases?

Also, scenarios where multi-tier Rancher might be employed due to sheer scale is an important factor to consider.

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jun 21, 2024
@richard-cox
Copy link
Member

Just in terms of managing large number of resources (upstream clusters, bindings, namespaces, etc and downstream pods, secrets, configmaps, etc), this will be covered by the pagination work. This covers not only lists but removing places where we fetch all of a resource to show summary / additional information.

Multi-tier rancher's would be a specific use case where i think the promise involve abstracting states up the chain

@aalves08
Copy link
Member Author

Yes, in fact all of that performance work is going to make it much easier to manage k8s resources at scale with Dashboard.

The idea here is more in line of offering a different overview to those use cases, especially in a multi-tier scenario, where I believe the end user (depending on it's role) might benefit from rather than the traditional Rancher view. Abstracting states up the chain is a must for this to work, for sure.

I am thinking even in different overviews for different roles of k8s admin, which might be a plus for XL-k8s-management enterprises.

Food for thought after attending Susecon 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants