Closed sbernauer closed 5 months ago
I'd like to see a refinement done on this before starting the work according to our template.
done
As we only use listener-op for HDFS and https://github.com/stackabletech/hdfs-operator/pull/534 got merged, IMHO we can close this. WDYT @razvan?
Update: This issue has been rescoped from adding labels to all volumes to just adding labels to the listener volumes. This means the scope has been reduced from refactoring all operators to only refactoring the op-rs and the hdfs operator.
Title
Ensure all listener ephemeral volumes have recommended labels.
Description
Currently there are two different ways to attach listener volumes to hdfs pods:
namenodes
: use volume claims. These inherit labels from the spec.template of the StatefulSet and are fine.datanodes
: uses volumes attached directly to the pod. These do not inherit the labels of the StatefulSet and are the reason of this issue. Because of this, the endpoints are not listed bystackablectl stacket list
.Update: this was the original description. Keeping it for later reference:
Value
stackabletctl stacklet list
can list bothnamenodes
anddatanode
endpoints.Dependencies
none
Tasks
ListenerOperatorVolumeSourceBuilder
in operator-rs ensures that recommended labels attached to the ephemeral and persistent volume explicitely.Related PRs
Acceptance Criteria
Listener ephemeral and persistent volumes have labels
(Information Security) Risk Assessment
Accessibility Assessment
Quality
Release Notes
No entry