operator: Add multicluster PVC unbinder controller#1454
Merged
RafalKorepta merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
RafalKorepta
requested review from
andrewstucki,
chrisseto,
gene-redpanda and
hidalgopl
as code owners
hidalgopl
approved these changes
Apr 16, 2026
The single-cluster PVC unbinder remediates Pods stuck in Pending due to volume node affinity conflicts by deleting the bound PVCs and recycling PVs. In multicluster mode (StretchCluster with NodePools across clusters), the same remediation is needed but the controller must resolve the correct per-cluster client for each Pod. Add MulticlusterController that registers with the multicluster builder to watch Pods across all provider clusters. On each reconcile it resolves the cluster client from req.ClusterName and delegates to the existing single-cluster Controller, reusing the full unbinding algorithm unchanged. Wire up --unbind-pvcs-after, --allow-pv-rebinding, and --unbinder-label-selector flags in the multicluster command, matching the existing flags in the single-cluster run command.
RafalKorepta
force-pushed
the
rk/k8s-834/add-pvc-unbinder
branch
from
d37311d to
fbff9c4
Compare
Contributor
|
@RafalKorepta does this need to be plumbed through the helm chart? |
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
3 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 single-cluster PVC unbinder remediates Pods stuck in Pending due to volume node affinity conflicts by deleting the bound PVCs and recycling PVs. In multicluster mode (StretchCluster with NodePools across clusters), the same remediation is needed but the controller must resolve the correct per-cluster client for each Pod.
Add MulticlusterController that registers with the multicluster builder to watch Pods across all provider clusters. On each reconcile it resolves the cluster client from req.ClusterName and delegates to the existing single-cluster Controller, reusing the full unbinding algorithm unchanged.
Wire up --unbind-pvcs-after, --allow-pv-rebinding, and --unbinder-label-selector flags in the multicluster command, matching the existing flags in the single-cluster run command.
K8S-834