Before you start
- New installation with PostgreSQL metadata and persistent Bytebase data
- Complete administrator setup before sharing; existing installations require upstream upgrade review
Configuration that needs your attention
Replaces the unavailable 3.3.0 image candidate with verified multi-architecture 3.22.1 manifests.
PG_URL is assembled from the same scoped password used by the database. No duplicate URL credential or embedded database is used. Back up both metadata and /var/opt/bytebase.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
database-password
Use this preset
- Open the Catalog in your own Hakopod dashboard and select Bytebase.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.