Skip to content

fix(operator): key a pool's allowed-node label on its UUID - #505

Merged
boddumanohar merged 1 commit into
mainfrom
fix/pool-node-label-63-byte-limit
Sep 9, 2026
Merged

boddumanohar merged 1 commit into
mainfrom
fix/pool-node-label-63-byte-limit

Conversation

@boddumanohar

@boddumanohar boddumanohar commented Sep 9, 2026 •

Copy link
Copy Markdown
Member

The pool's allowed-node label key was built from the namespace, the cluster name, and the pool name, which can exceed the 63 bytes a label name allows. This is causing e2e test to fail.

simplyblock.io/pool.cluster1.simplyblock-cluster-a.e2e-dhchap-sched-spdkcsi-8108
name part must be no more than 63 bytes

The API server refused the key, so the allowed node was never labeled and the pool could not be deleted either, since the deletion path writes the same label. It failed the nightly GCP e2e (SPDKCSI-DHCHAP).

The key is now storage.simplyblock.io/pool.<pool UUID> — 41 bytes whatever anything is named. The derivation and its two constants move to atlas-lib/kube, and the CSI driver and the e2e spec use them instead of their own copies.

@boddumanohar
boddumanohar force-pushed the fix/pool-node-label-63-byte-limit branch 2 times, most recently from 1d00f8f to f11499d Compare September 9, 2026 09:25
@boddumanohar
boddumanohar merged commit cde2b63 into main Sep 9, 2026
19 checks passed
@boddumanohar
boddumanohar deleted the fix/pool-node-label-63-byte-limit branch September 9, 2026 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants