Tutorials
Choose a path by what you want to operate. Most application work happens inside a Project. Kubernetes platform software belongs in a Managed Cluster.
First session
- Sign up and sign in
- Understand Organizations, Projects, and Managed Clusters
- Create your first Project
- Configure CLI access
- Deploy your first application
Run an application in a Project
- Projects explains the supported API boundary.
- Deploy a WordPress stack combines an app with managed services.
- Service exposure publishes HTTP, HTTPS, TCP, or UDP.
- Scaling and performance sizes a workload from measurements.
- GitOps delivers from an external controller or from CI.
The {organization}-{project} namespace backs each Project. Use the Project
name in prose, and the backing namespace only in YAML or in kubectl commands.
Run a virtual machine
- Create a virtual machine
- Connect to the VM
- Manage the VM lifecycle
- Choose block storage
- Configure external or floating IPs
Use managed data services
- Managed services: databases, caches, and brokers from the catalog
- Credentials and rotation
- Object storage
- Secrets Manager
- Key management
- Data protection and recovery
Operate a Managed Cluster
Use a Managed Cluster when an application needs its own Kubernetes API, operators, CRDs, multiple namespaces, or cluster-scoped administration.
- Provision a Managed Cluster
- Manage workers, storage, exposure, and upgrades
- Install GitOps in the Managed Cluster
Managed Cluster workers consume quota from the parent Project.
Manage access and security
Organization admins manage membership and Project role assignments. Project roles do not remove the platform admission policies that protect shared infrastructure.
Platform operator guides
Installation, shared networking, identity-provider configuration, and platform recovery are operator responsibilities. They are documented separately in the Platform guide. Project users should not run platform-cluster commands from tenant tutorials.