sync: support all-in-one mode + API sync#1449
Open
kenjenkins wants to merge 1 commit into
Open
Conversation
When syncing to Pomerium Enterprise, there is a chicken-and-egg problem: Enterprise relies on Pomerium Core to authenticate all incoming API requests. But the route to Enterprise itself is defined using an Ingress, so we can't communicate with the API at all before the route exists. Instead, let's expand the scope of the "bootstrap" configuration that gets passed directly from ingress-controller to Core via the in-memory ConfigSource. When in the API sync mode, include any Ingress-defined routes that match the configured API sync URL. Also include additional settings that can't be applied via the Enterprise API.
kenjenkins
force-pushed
the
kenjenkins/sync-all-in-one
branch
from
f06a9a1 to
5173810
Compare
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
When syncing to Pomerium Enterprise, there is a chicken-and-egg problem: Enterprise relies on Pomerium Core to authenticate all incoming API requests. But the Pomerium route to Enterprise is itself defined using an Ingress, so we can't communicate with the API at all before this route exists. We can't use the API to create the route to the API.
Instead, let's expand the scope of the "bootstrap" configuration that gets passed directly from ingress-controller to Core via the in-memory ConfigSource. When in the API sync mode, include any Ingress-defined routes that match the configured API sync URL.
Related issues
https://linear.app/pomerium/issue/ENG-3854/bootstrap-deadlock-api-reconciler-mode-cannot-reach-console-when
AI disclosure
Claude Code drafted unit tests for the
bootstrapIngressManagertype. I reviewed and simplified these test cases.Checklist
improvement/bug/ etc)