fix(foundry): route sentinel service-account and analytics paths to core - #164
Merged
Merged
Conversation
gauchoracing
approved these changes
Aug 26, 2026
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
2 participants
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 kerbecs ConfigMap was never updated when service accounts shipped, so
/api/service-accounts/*has no route and falls through to theweb-frontendcatch-all. nginx's SPA fallback answers200+index.html, axios resolves it as success, and the reveal dialog renders an empty token instead of erroring. Rotate and delete get a405from nginx.core-service-accountsroute (/api/service-accounts/*→ core) — fixes reveal / copy / rotate / delete on the application service-accounts cardcore-analyticsroute (/api/analytics/*→ core) — needed by the analytics hub landing in feat(analytics): analytics hub with aggregation endpoints and audit trail Sentinel#110; without it every analytics call gets SPA HTML with a 200Verified by running
bk1031/kerbecs:3.2.0against this exact ConfigMap (upstreams repointed at local stubs): all SA + analytics paths now reach core with/apistripped, and SPA routes still fall through to web.No manual steps —
providers.static.watch: truehot-reloads the mounted config, so no kerbecs restart is needed. No Vault secrets or access rules involved.