Tasks
Use gh0stcloud
Task map for operating gh0stcloud through gh0stportal, GitOps, and the example repository.
gh0stcloud is operated through two surfaces:
- gh0stportal for tenant state, projects, namespaces, GitOps binding, storage intent, exposure intent, observability, billing, and requests.
- Your GitOps repository for application manifests, Helm releases, ingresses, PVC references, and app-level configuration.
Use the public example repository as a reference, not as a source of tenant truth: gh0stservice/ghc-gitops-example.
Common tasks
| You want to | Use this portal page | Read this doc | Example repo reference | gh0stplane surface |
|---|---|---|---|---|
| Check what needs attention | Home | This page | docs/01-overview.md | GetTenantHomeWorkspace, GetTrialOnboardingWorkspace |
| Create a project or namespace | Applications | Projects and Namespaces | kustomize/overlays/ghc-basic | GetTenantApplicationsWorkspace, project/namespace CRUD |
| Connect your GitOps repo | Applications | GitOps and Secrets | docs/02-gitops-binding.md | UpdateTenantGitOpsBinding |
| Find OpenBao secret paths | Applications | GitOps and Secrets | ExternalSecret examples | GetTenantSecretWorkflow |
| Add a persistent volume | Data & Services | Storage, Services, and Backups | docs/03-storage-and-services.md | storage volume CRUD |
| Add a managed database or service | Data & Services | Storage, Services, and Backups | service examples when available | managed service CRUD |
| Expose a service publicly | Network & Exposure | Network and Exposure | docs/04-network-and-ingress.md | exposure workspace and intent RPCs |
| Use your own domain | Network & Exposure | Network and Exposure | BYOD notes | hostname validation and exposure requests |
| Add egress or service-to-service traffic | Network & Exposure | Network and Exposure | network policy examples | network workspace and intent RPCs |
| View logs, metrics, and first-app diagnostics | Observability | Observability and Troubleshooting | troubleshooting notes | observability, home, network, data workspaces |
| Review invoice/payment state | Billing | Billing and Change Requests | docs/05-billing-and-costs.md | customer billing RPCs |
| Request more limits or privileged changes | Change Requests | Billing and Change Requests | n/a | tenant change-request RPCs |
| Ask an AI agent to create manifests | Docs + example repo | Agent Guide | full repository | same task map, never direct cluster writes |
Work from the portal outward
- Start in Home and handle the first pending next step.
- Use Applications to create/select a namespace and connect GitOps.
- Use Data & Services before deploying stateful apps.
- Use Network & Exposure before adding public hostnames or egress.
- Use Observability to confirm runtime behavior.
- Use Billing to check trial state, invoices, and payment setup.
- Use Change Requests when the action is outside current tenant bounds.
Safety rules
- Do not invent tenant hostnames, namespace names, OpenBao paths, or service accounts. Copy them from gh0stportal.
- Do not commit secrets to Git. Put secret values in OpenBao and reference them through External Secrets.
- Do not treat projects as an access boundary. Projects are product grouping; namespace and tenant policy enforce runtime boundaries.
- Do not bypass the request flow for limits, egress expansion, operator enablement, assignment mode, or exposure bounds.
- Do not assume the example repo is production-ready for every app. It is a vocabulary and manifest reference.
Agent entrypoint
If you work with a coding agent, start with Agent Guide and the example repository. The agent should ask for tenant-specific values from gh0stportal output instead of guessing them.
Questions or ready to get started?
Talk to us