Deploy: point biosim-gke at backend-0.10.0 and frontend-0.2.0 - #100
Merged
Conversation
Merging this is the deploy: Flux reconciles kustomize/overlays/biosim-gke into the biosim-gke namespace, so the cluster follows within a minute. All three images are published -- the backend-v0.10.0 and frontend-v0.2.0 release runs succeeded and both GitHub Releases are cut. Verifying that before merging matters now: api runs the Recreate strategy at one replica, so pointing the overlay at an unpublished tag would take the API down rather than leaving the old pods serving. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MfRrxjsddsBLcFeNCXSBcU
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.
Summary
Points the
biosim-gkeoverlay at the images published bybackend-v0.10.0and
frontend-v0.2.0(cut from #99).
Merging this PR is the deploy. Flux now reconciles
kustomize/overlays/biosim-gke, so the cluster followsmainwithin a minute —no
kubectl apply.platform-apibackend-0.9.2backend-0.10.0platform-workerbackend-0.9.2backend-0.10.0platform-frontendfrontend-0.1.1frontend-0.2.0Pre-flight
All three images verified published before opening this: both release runs
completed successfully (api, worker, frontend build jobs all green) and both
GitHub Releases are cut. That check is load-bearing now —
apiuses theRecreatestrategy at a single replica, so an unpublished tag here means anAPI outage rather than old pods continuing to serve.
What goes live
Auth0 authentication reaches the cluster for the first time: bearer-token
verification on the backend, owner-or-admin gating on simulation cancel/delete,
and the login / signup / forgot-password UI on the frontend. The
biosim-gkeConfigMaps already carry
AUTH0_DOMAIN,AUTH0_AUDIENCE, and theNUXT_PUBLIC_AUTH0_*values, so the configured path works.Two known gaps, neither blocking:
AUTH0_MANAGEMENT_CLIENT_ID/_SECRETare not set in the cluster, soPATCH/DELETE /api/v1/mewill fail there.GETis unaffected.gate — an incomplete Auth0 config would fail requests rather than crash-loop
visibly. The config is complete, so this is a diagnosability gap, not a
functional one.
Also shipping: OMEX
./manifest fix (#90), simulator versions sortednewest-first (#91), the frontend QOL batch (#95), and the
NUXT_PUBLIC_LEGACY_API_URLfix for project-detail 404s.Rollback
Revert this commit. Flux reverts the cluster on the next reconcile.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MfRrxjsddsBLcFeNCXSBcU