Kubernetes
You get a Kubernetes namespace, your own kubeconfig, and the platform's operators already running in the cluster. What follows is what is specific to this platform: what you may create, how traffic reaches you, and what you are billed for.
Start here
| Page | What it covers |
|---|---|
| Access and kubectl | Kubeconfig, setting up kubectl, default namespace, credential validity |
| Your first deployment | Deployment, service and HTTPRoute through to a working HTTPS address |
| Deploying from Git | Point your namespace at a repository, or deploy from CI |
| Images and pull secrets | The ITSH registry and private registries elsewhere |
| Secrets and configuration | Secrets, config maps, and object storage credentials |
| Jobs and CronJobs | One-off tasks and scheduled work |
Reference
| Page | What it covers |
|---|---|
| Gateway API | HTTPRoutes, which hostnames you may use, automatic HTTPS, custom domains |
| Networking | What your workloads can reach, inbound and outbound |
| Storage | Storage classes, billing minimum, PVC autoresize |
| Databases | PostgreSQL, MariaDB and Dragonfly via operators |
| Autoscaling | HPA, KEDA and VPA |
| Scale-to-zero | Letting an HTTP service sleep, and what it costs |
| Permissions and policies | What RBAC grants, which platform rules reject a manifest |
| Versions and defaults | API versions to write, and what your namespace fills in |
| What the portal shows you | Usage, cost, right-sizing suggestions, spending cap |
| Billing and quotas | Billing on requests, storage, egress |
| Free tier | Quotas, restrictions, suspension rules |
When something is broken
Troubleshooting is indexed by symptom, so start from the error you are actually seeing rather than from what you think caused it.
Who this is for
Anyone deploying their own workloads and writing their own YAML. The pages assume working knowledge of Kubernetes and focus on what is specific to this platform.
Examples are deliberately short and show only the fields that matter. Where an example contains <your-namespace>, replace it with your own namespace name, which is shown in the portal next to the kubeconfig.