Create the first cluster

Create a disposable Development cluster for evaluation. Do not create a production cluster until its entire Hardened contract is complete.

Before you begin

• Verify the controller and Provisioner are available.
• In multi-tenant mode, confirm OpenBaoTenant.status.provisioned: true and the tenant RoleBinding.
• In single-tenant mode, confirm that the controller’s WATCH_NAMESPACE equals the target namespace.
• Confirm a default StorageClass exists for evaluation. Choose the StorageClass and capacity explicitly for production.
• Decide whether the cluster is disposable or intended for production before the first reconcile.

Choose the profile

spec.profile is required. Changing the word Development to Hardened does not complete the production contract.

Create an evaluation cluster

1. Save this manifest as cluster.yaml.

   configure

   Declare the evaluation cluster

   Copy

   apiVersion: openbao.org/v1alpha1
      kind: OpenBaoCluster
      metadata:
        name: dev-cluster
        namespace: openbao-demo
      spec:
        version: "2.6.0"
        replicas: 1
        profile: Development
        tls:
          enabled: true
          mode: OperatorManaged
          rotationPeriod: "720h"
        storage:
          size: "10Gi"
        deletionPolicy: Retain

   Replace openbao-demo only with a namespace authorized by the chosen tenancy model. Version 2.6.x is the primary current validation line; the manifest pins the concrete version exercised by current CI.

2. Apply the manifest.

   apply

   Create the cluster

   Copy

   kubectl apply -f cluster.yaml

3. Watch the custom resource and Pods converge.

   inspect

   Watch cluster creation

   Copy

   kubectl -n openbao-demo get openbaocluster dev-cluster -w
      kubectl -n openbao-demo get pods \
        -l openbao.org/cluster=dev-cluster -w

4. Wait for the availability condition.

   verify

   Wait for cluster availability

   Copy

   kubectl -n openbao-demo wait \
        --for=condition=Available \
        openbaocluster/dev-cluster \
        --timeout=10m

5. Inspect the final status and storage.

   verify

   Verify status and persistent storage

   Copy

   kubectl -n openbao-demo get openbaocluster dev-cluster -o yaml
      kubectl -n openbao-demo get pods,pvc,services \
        -l openbao.org/cluster=dev-cluster

   Confirm:

   • status.phase is Running;
   • status.readyReplicas equals spec.replicas;
   • Available=True and TLSReady=True;
   • every voter Pod is Ready and its PVC is Bound;
   • the TLS mode and storage match the declared configuration.

Prepare a Hardened cluster

A complete production manifest must define all of these contracts before the first reconcile:

1. Set profile: Hardened and at least three replicas.
2. Configure tls.mode: External or ACME and verify the issuer, Secret, domain, and termination boundary.
3. Configure a non-static unseal provider and its workload identity or Secret references.
4. Enable self-init and provide a non-empty request list.
5. Enable operator OIDC when lifecycle Jobs will use projected JWT authentication.
6. Create at least one usable human authentication path in selfInit.requests before root-token revocation.
7. Set persistent storage and deletion policy explicitly. Account for the current lack of voter resource controls before production.
8. Configure and test backup identity, object storage, and restore before the first risky change.
9. Define network egress for external unseal, backup, issuer, or discovery dependencies.

Use the configuration baseline for these choices. Do not publish an incomplete Hardened YAML block as if it were executable.

Troubleshoot the first reconcile

Continue with production operations.