docs(k8s): app-only — account for the dedicated tpk database - #61
Merged
Conversation
The k8s manifests (#56/#57) predate the change that moved all tpk streams under a dedicated `tpk` database (#59). For app-only — which connects to an externally-managed Timeplus Enterprise — the app now runs `CREATE DATABASE IF NOT EXISTS tpk` on startup, so the pre-existing DB user needs CREATE DATABASE (first run) plus read/write on that database. A restricted user would otherwise fail at startup/ingest. - app-only.yaml: header now states the app creates its own database on the existing server; add a `TIMEPLUS_DATABASE` env (default `tpk`) with the privilege note and the pre-create fallback for restricted users. - deploy/k8s/README.md: add a "tpk database" note to the App-only section (CREATE DATABASE grant + pre-create SQL), and a TIMEPLUS_DATABASE row to the Configuration table. Notes that enterprise/allinone are unaffected (they provision a full-privilege tpk user). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XPzYZXxyTdj5G25KoujpHb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The k8s manifests (#56/#57) were written before the
tpkdatabase change (#59). This updates the app-only mode, which is the one materially affected.Why
app-only connects to an externally-managed Timeplus Enterprise. Since #59, the app runs
CREATE DATABASE IF NOT EXISTS tpkon startup and puts all streams undertpk. So the pre-existing DB user now needs CREATE DATABASE (first run) plus read/write on that database — a restricted user would fail at startup/ingest with no hint why. The old manifest even said "Nothing here provisions or runs a database," which is now slightly misleading (it doesn't run a DB server, but it does create thetpkdatabase).Changes
app-only.yaml: header clarifies the app creates its own database on the existing server; adds aTIMEPLUS_DATABASEenv (defaulttpk) with the privilege note and a pre-create fallback for restricted users.deploy/k8s/README.md: a "tpk database" note in the App-only section (CREATE DATABASE grant + pre-create SQL), and aTIMEPLUS_DATABASErow in the Configuration table.enterprise.yamlandallinone.yamlare unaffected — they provision a full-privilegetpkuser, so database creation just works; noted as such.Validation
Parsed
app-only.yaml:TIMEPLUS_DATABASE=tpkpresent, still no DB server object.🤖 Generated with Claude Code