Clients: Kubernetes for many clients, organized
To manage Kubernetes for many clients, Kubepier ties every cluster to a client: the company you serve or an internal team. That is how you find the right cluster among dozens.
How Kubepier organizes clusters for many clients
- A name and a color, shown in the catalog and on every cluster screen.
- A keyword: a cluster whose name contains it joins the client automatically.
- The access to its services (RabbitMQ, Azure Service Bus, MongoDB and Redis). Each saved access becomes a client menu.
- On the web, the optional Folder field when creating or editing a client (admins): the client list is grouped by folder, with a filter, and the client picker splits clients by folder.
- On the web, the home screen with each client’s health: clusters, failing pods and warnings.
What is accepted
- Name required; color and keyword optional.
- On the web, each service access is saved separately and can be removed on its own; the service menu goes with it.
What is not accepted
- On the web, members do not create, edit or see saved access. Credentials never come back to the screen, not even for admins.
Where it lives and who sees it
- Web: in the Clients menu. Desktop: under Preferences › TR Clients.
- Per-client access only exists on the web: admins see every client and members the ones granted to them. On desktop, each person sees the clients saved on their own machine.
- Service access is encrypted: in the database with AES-256-GCM (web) or by the OS keychain (desktop).