How it works

KubeBrowser is an Operator

KubeBrowser is an Operator, hence it has been designed to be hosted on Kubernetes. KubeBrowser watches its CustomResourceDefinition (CRD) and always renders an up-to-date view on the UI.

Kubeconfig CRD

Kubeconfig is the main component of Kubebrowser. You can create as many Kubeconfig as you want. Each Kubeconfig roughly represents a cluster, and is automatically displayed on Kubebrowser UI. See kubeconfig reference for details on the resource.

OpenID Connect

KubeBrowser leverages your OIDC provider to:

1. Show only the Kubeconfigs your user has been whitelisted to see.
2. Fill the Kubeconfig users section so it is ready to use.

WARNING

Currently, KubeBrowser uses a unique OIDC configuration for all the Kubeconfigs, this could change in the future depending on the community feedback and needs.