Storage, Services, and Backups

Use Data & Services before deploying stateful workloads. gh0stportal shows which storage classes, managed services, protection bindings, and restore points are available for your tenant.

Create a persistent volume

Open Data & Services.
Choose the namespace that will own the app.
Create a storage volume intent with size, class, and access mode.
Review quota, backup, and cost-impact hints.
Save and wait for reconcile state.
Add the matching PVC reference to your GitOps app manifests.

The portal-owned volume intent is the platform contract. Your GitOps manifests still need to mount the PVC in the workload.

Managed services

Managed services are provisioned through gh0stcloud capabilities and policy bounds. If the New Service action is disabled, read the disabled reason instead of trying to work around it in GitOps.

Common prerequisites:

namespace exists and is reconciled;
required operator capability is allowed;
quota and policy bounds are sufficient;
storage/protection requirements are understood.

Backups depend on the protection strategies available to your tenant. The portal shows default policies and binding choices where available. If a needed backup strategy is not available, use the request flow instead of creating platform-level backup resources in GitOps.

GitOps reference

Read:

example storage docs
kustomize/overlays/ghc-advanced

RPC/function map

Portal action	gh0stplane surface
Load data workspace	`GetTenantDataWorkspace`
Create/update/delete volume intent	`CreateTenantStorageVolume`, `UpdateTenantStorageVolume`, `DeleteTenantStorageVolume`
Create/update/delete managed service	`CreateTenantManagedService`, `UpdateTenantManagedService`, `DeleteTenantManagedService`
Create/update/delete protection binding	`CreateTenantDataProtectionBinding`, `UpdateTenantDataProtectionBinding`, `DeleteTenantDataProtectionBinding`

Common mistakes

Symptom	Likely cause	Fix
App starts without data	Workload did not mount the portal-created PVC.	Add the PVC mount to GitOps.
PVC is missing	Intent exists but GitOps app does not request or mount it yet.	Compare Data & Services with the manifest.
Service creation is blocked	Operator, quota, namespace, or policy prerequisite is missing.	Read the disabled reason and use Change Requests if needed.