feat(009,012): re-pin the Deployment to the spec 012 operator-dashboard image#56
Merged
Conversation
…rd image Digest ce8edee5 (tag dfe27c1, the PR #55 merge): backend/obs/ + the gated admin surface + the frontend-admin bundle + app-model.json enter production, alongside the first deploy of the spec 011 tenant-lifecycle code. The one-time user_account ALTER (spec 011 §9) was applied to the live database before this pin; RAUTHY_API_KEY stays an open spec 011 operator act and degrades gracefully. Spec 009 records the re-pin.
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.
Pins the control-plane Deployment to digest
ce8edee5(tagdfe27c1, the PR #55 merge): the first image carrying the spec 012 operator dashboard (backend/obs//metrics+ trace plane, the gated/adminsurface,app-model.json) and the spec 011 tenant-lifecycle code.Pre-pin state changes already applied to the live cluster:
ALTER TABLE user_account ADD COLUMN github_user_id TEXT; ADD COLUMN github_login TEXT;(stamp_job's precursor columns already existed), so the new image's auth store boots against a compatible schema.Known-open, deliberately not blocking:
RAUTHY_API_KEY(spec 011 operator act, minted in rauthy admin); github-identity resolution logsno_api_keyand skips until it exists.On merge, Flux reconciles: the pod Recreates onto the new image together with the already-merged
ADMIN_UI_ENABLEDenv, theprometheus.ioscrape annotations, and the/metricsdeny Ingress. Live verification of spec 012 acceptance follows, then the spec flips to complete in a docs PR.