identity/edge producer: optional --cluster-id to scope uploads per cluster#51
Merged
Conversation
…uster The download-api isolates identity and policy-edge baselines per tenant (org/workspace) automatically. When more than one cluster shares a single workspace, uploads still collide, so add an optional --cluster-id that tags this cluster's baseline with a `?cluster=<id>` sub-scope on the identity/policy-edges upload URLs. Empty (the default) keeps the un-clustered path. To isolate, set a stable unique value here and the matching cluster id on every agent in this cluster. No auto-derivation: the agent runs on bare VMs too and has no cheap way to derive the same value, so an auto-default would silently mismatch the consumer.
Extends --cluster-id to the incremental delta path: the emitted IdentityDelta/EdgeDelta now carry the source cluster, so an agent in a workspace shared by multiple clusters can ignore deltas from other clusters. Empty when --cluster-id is unset (single-cluster default).
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.
Companion to the download-api tenant-scoping of identity/policy-edges
artifacts.
The download-api isolates these baselines per tenant (org/workspace)
automatically from the authenticated key. That covers the common case of
one cluster per workspace. When more than one cluster shares a single
workspace, uploads still target the same tenant path and overwrite each
other.
This adds an optional
--cluster-idto the identity and edge producers.When set, it appends a
?cluster=<id>sub-scope to the upload URLs soeach cluster gets its own isolated baseline.
change for existing single-cluster deployments.
id on every agent in this cluster.
with no cluster API to read the same value, so an auto-default would
silently mismatch producer and consumer. Isolation is explicit opt-in.