operator: register every cluster of the control plane with the CSI driver - #619
Merged
schmidt-scaled merged 2 commits intoOct 3, 2026
Merged
Conversation
…iver A volume replicated to another site is promoted there under a PV that keeps the handle it was created with, which names the cluster the volume came from: that site's driver must be able to reach the control plane for that cluster too. Until now each operator wrote only its own cluster into simplyblock-csi-secret-v2, and the cross-registration was a manual merge of the sites' secrets (realbed deploy.sh csi). Each operator now writes, next to its own cluster (marked local, the flag the driver's replication-chain resolver keys on), one entry per other cluster the control plane lists, with the secret the list carries -- empty when the control plane withholds it, and the driver then authenticates with its API token. Entries another operator on the same Kubernetes cluster marked local are left alone; a foreign entry whose cluster the control plane no longer lists is dropped. The own entry never waits on the list: when the list cannot be read, peers are registered on the next sync. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…/simplyblock-operator into feat/csi-auto-cross-registration # Conflicts: # operator/internal/controllers/cluster/storagecluster_controller.go
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.
Summary
simplyblock-csi-secret-v2; the cross-registration was a manual merge of the sites' secrets.local: true, the flag csi-driver: replication RPCs resolve the right chain member; a plan without fsType mounts what the volume carries #618's replication-chain resolver keys on), one entry per other cluster the control plane lists, with the secret the list carries (empty when withheld → the driver's API token). Other operators' local entries are left alone; foreign entries for clusters no longer listed are pruned. The own entry never waits on the list.CSIClusterEntry.Localhunk as csi-driver: replication RPCs resolve the right chain member; a plan without fsType mounts what the volume carries #618 so both merge cleanly.Test plan
mergeCSICredentials— registers peers, keeps another local entry, prunes stale foreign entries, keeps a recorded secret the list withholds, own-only without the listdeploy.sh csi🤖 Generated with Claude Code