What web UI should I provide for internal Kubernetes users?

Headlamp is not the only option. Lens is another familiar choice, though its licensing and the distinction between the desktop and web experience may be drawbacks. The older Kubernetes Dashboard is generally not a good direction because it’s deprecated and no longer actively maintained.

Radar could be a good fit. It can run in the cluster, supports OIDC/Keycloak, and honors each user’s Kubernetes RBAC permissions. Its focus is less on exposing every object individually and more on showing relationships, topology, changes, issues, and GitOps context, which may be easier for developers who aren’t Kubernetes specialists.

Argo CD is a solid choice if the main workflow is GitOps. It provides a useful deployment and application dashboard, but it isn’t really a general-purpose Kubernetes console for arbitrary cluster operations. Whether it fits depends on what users actually need to do.

Rancher is worth evaluating, especially if you want one interface for multiple clusters. It supports centralized cluster management and access control, although some areas—particularly applications and charts—can feel slow depending on the scale and workload.

For data-science-oriented users, Onyxia may be worth a look. It includes integrations around Keycloak/OIDC and persistent S3-backed storage, so it can be more suitable than a generic cluster browser when users need to launch and manage data tools.