Environments

Environment	Where	Notes
Production	OKE in ap-hyderabad-1, namespace startupos. Hosts rtih.peoplewave.in, api.rtih.peoplewave.in, app.rtih.peoplewave.in, livekit.rtih.peoplewave.in.	The only environment this site documents in detail. Observed on 2026-11-07.
Staging	A second git remote named oci points at an OCI DevOps repository in the Mumbai region.	Listed in .kiro/steering/project-commands.md. Whether a staging cluster is running was not checked. Unverified.
Local development	infra/k8s/local/ manifests and deploy-local.sh, or mvn quarkus:dev per service.	deploy-local.sh refuses production, OKE, OCI and staging contexts.

Git remotes

The repository has three remotes: origin (GitHub), oci (staging, Mumbai) and oci-prod (production, Hyderabad). The production remote holds the repository that OCI DevOps pipelines build from. Whether the pipelines are the path used for current releases is unverified: recent releases were patched onto live Deployments by hand, as described in Build and deploy.

Configuration

• Non-secret settings: the ConfigMap startupos-config.
• Secrets: the Secrets startupos-secrets, startupos-oidc-client, keycloak-secrets, keycloak-identity-admin-client, livekit-secret and ocir-secret. Their names appear in manifests. Values never belong in git. The runbook docs/runbooks/prod-out-of-band-resources.md lists what exists outside the repository.
• Each Deployment sets QUARKUS_OIDC_ENABLED=true and QUARKUS_OIDC_TENANT_ENABLED=true on its container.

Sources: .kiro/steering/project-commands.md, infra/k8s/local/deploy-local.sh, docs/runbooks/prod-out-of-band-resources.md, secret names read from the cluster on 2026-11-07 (names only).