Tutorials

Choose a path by what you are trying to operate. Most application work happens inside a Project; Kubernetes platform software belongs in a Managed Cluster.

First Session

1. Sign Up and Log In
2. Understand Organizations, Projects, and Managed Clusters
3. Create Your First Project
4. Configure CLI Access
5. Deploy Your First Application

Run an Application in a Project

• Projects: understand the supported API boundary
• Deploy a WordPress Stack: combine an app with managed services
• Service Exposure: publish HTTP, HTTPS, TCP, or UDP
• Scaling and Performance: size from measurements
• GitOps: deliver from an external controller or CI

A Project is backed by the {organization}-{project} namespace. Use the Project name in product language and the backing namespace only in YAML or kubectl commands.

Run a Virtual Machine

1. Create a Virtual Machine
2. Connect to the VM
3. Manage the VM Lifecycle
4. Choose Block Storage
5. Configure External or Floating IPs

Use Managed Data Services

• Managed Databases
• Database Credentials
• 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.

1. Provision a Managed Cluster
2. Manage Workers, Storage, Exposure, and Upgrades
3. Install GitOps in the Managed Cluster

Managed Cluster workers consume quota from the parent Project.

Manage Access and Security

• User and Group Management
• Security Restrictions
• Certificate Management

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 customer tutorials.