Kubernetes epic: Add "advanced" sections (daemonsets, statefulsets, jobs, etc.)

containers / podman-desktop

Podman Desktop is the best free and open source tool to work with Containers and Kubernetes for developers. Get an intuitive and user-friendly interface to effortlessly build, manage, and deploy containers and Kubernetes — all from your desktop.

https://podman-desktop.io

Apache License 2.0

4.72k stars 298 forks source link

Kubernetes epic: Add "advanced" sections (daemonsets, statefulsets, jobs, etc.) #7192

Open cdrage opened 5 months ago

cdrage commented 5 months ago

Epic domain

There are other parts of Kubernetes that could be added such as "advanced" that could possibly be toggled / shown as an advanced section.

The missing ones would be:

Should be added:

[ ] DaemonSets
[ ] StatefulSets
[ ] ReplicaSets
[ ] Jobs
[ ] CronJobs

IMHO should not be added / super advanced features:

Ingress Classes (more administrative)
Storage Classes (more administrative)
Replication Controllers (controlled by deployments, seldom used)
Resource Quotas (admin use)
Limit Ranges (admin use)
HPA (admin use, usually created by deployment)
Pod Disruption Budgets (admin)
Priority classes (admin)
Runtime classes (admin)
Leases (admin)
Mutating webhook configs (admin)
Validating webhook configs (admin)
Endpoints (not needed / created by service)
Network Policies (admin)
Port Forwarding (maybe?)

Additional context

No response

axel7083 commented 5 months ago

I fear this will not scale in the navbar.. I am against adding all the kubernetes resources in the navbar, even through an advanced flag.

IMO we should only have a Kubernetes icon on the navbar, opening it would lead to a dedicated page, or webview if we want to externalize it.

Here is a quick mockup, you will clearly see the inspiration from Lens, as it is a tool I am using since a very long time, i feel confortable have all the Kubernetes resources listed in a navigation bar, and it would scale well to those advanced scenarios.

cc @slemeur some opinion ?

deboer-tim commented 5 months ago

It is also a question for design, but this issue says 'we should have it', not 'we should have it in the navigator'. Let's not spend time figuring out where future things might go until we are planning to start it.

slemeur commented 5 months ago

@axel7083 : I agree that the current navigation for the kubernetes objects does not scale and feels undiscoverable. Between kubernetes objects, extensions, the navigation does not offer a proper way to handle a usable scalable navigation.

I'm +1 on the proposal you have. I also believe that we should match the pattern we have in the other extensions with the 2nd sidebar navigation.

slemeur commented 5 months ago

I would also like that we have all kubernetes objects under a single menu items. Right now, I don't see the reason why Pods have their primary entry, compared to the other Kubernetes objects (which are also supported by Podman)

cdrage commented 5 months ago

Updated the original issue that it's more of a suggestion, rather than "should".

I agree with the points from @slemeur regarding pods, it should be in the Kubernetes section..

We should 100% have a discussion the direction of advanced sections like these before continuing.