Complete hiding
Namespaces, objects and cluster-scoped resources outside a user’s access are dropped from lists and answered as not found.
Kubernetes accessGA
Everyone sees only what they should, in Kubernetes
Organization admins decide who reaches which cluster and namespace. Whatever a user cannot access is not even listed — all behind a fast caching API proxy.
Live
Capabilities
Kubernetes access
Fast caching
Read answers are cached per user; concurrent requests collapse into one and any write clears the cache.
Users and groups
Read-only, developer and admin roles for a cluster or specific namespaces.
kubectl with whyctl
whyctl login and kubectl without a permanent kubeconfig or an exposed cluster API.
Audit of every request
Every request is recorded with user, namespace and result.
WhyCloud users only
Limit access to users inside the WhyCloud organization or its SSO.
FAQ
Frequently asked questions
Can users tell other namespaces exist?
No. Lists show only what they may access and direct requests for anything else get “not found”.
Can the cache show stale data?
It is short-lived, separate per user, and cleared by any write (create, update, delete) on the same path.
Related services
Cloud Servers & VMswhycloud cloud servers: connect Linux hosts with one command, web term…PaaS container appswhycloud PaaS: give a Compose file or a docker run command and the app…GPU & parallel computeManage GPUs for AI training and inference on your own hardware: usage …Container registrywhycloud registry: on-prem on your server or cloud, proxy cache for Do…
Turn on your own cloud today
Create an account and connect your first server in under five minutes.