KubernetesComing in 1.1
Kubernetes without a second console.
Connect a cluster you already have, run k3s on your own servers, or create a managed cluster at your cloud. See and change it in the same panel, with the same permissions and the same audit log.
Not available yet. This page shows what is being built, so you can plan around it.
Managed clusters it can create
- DigitalOcean DOKS
- AWS EKS
- Google GKE
- Azure AKS
- OVHcloud MKS
- Akamai LKE
- Vultr VKE
- Scaleway Kapsule
- UpCloud UKS
How it works
Connect
Paste a kubeconfig or a service account token for a cluster you run.
Or create
Turn panel servers into a k3s cluster at a pinned version, or create a managed cluster through a cloud connection.
Deploy
Paste YAML or pick a chart from the catalog. Watch pods, read logs and open a shell.
What you get
-
Everything you look at
Nodes, namespaces, workloads, pods with logs and exec, services, ingresses, config maps, volumes, events and Helm releases.
-
Secrets stay masked
Secrets show as masked values. Changes are typed actions, not loose commands.
-
A namespace per account
Give a hosting account its own namespace with quotas and network policies. Its ingress hosts tie into your domains and certificates.
-
Helm charts
Install and upgrade releases from a catalog, with a preview before the change.
No shortcuts
- k3s is installed at a pinned version by the agent, never by piping a script into a shell.
- Changes are plans you can read before they run, like the rest of the panel.
- Shell access to pods goes through the agent's tunnel and is written to the audit log.
Questions
Is it available now?
No. Kubernetes is being built and is planned for 1.1. For Docker, Containers is in preview today.
Does it replace kubectl?
No. It gives you the daily work in a screen, with permissions and an audit log. kubectl keeps working.