sticky -> pinning

Author: sbernauer

crates/stackable-operator/CHANGELOG.md

@@ -6,7 +6,7 @@ All notable changes to this project will be documented in this file.
 
 ### Added
 
-- BREAKING: Add new `ListenerClass.stickyNodePorts` field ([#1105]).
+- BREAKING: Add new `ListenerClass.pinningNodePorts` field ([#1105]).
 
 [#1105]: https://github.com/stackabletech/operator-rs/pull/1105
 

crates/stackable-operator/crds/ListenerClass.yaml

@@ -70,15 +70,15 @@ pub mod versioned {
         /// Wether or not a Pod exposed using a NodePort should be pinned to a specific Kubernetes node.
         ///
         /// By pinning the Pod to a specific (stable) Kubernetes node, stable addresses can be
-        /// provided using NodePorts. The stickiness is achieved by listener-operator setting the
+        /// provided using NodePorts. The pinning is achieved by listener-operator setting the
         /// `volume.kubernetes.io/selected-node` annotation on the Listener PVC.
         ///
         /// However, this only works on setups with long-living nodes. If your nodes are rotated on
         /// a regular basis, the Pods previously running on a removed node will be stuck in Pending
-        /// until you delete the PVC with the stickiness.
+        /// until you delete the PVC with the pinning.
         ///
-        /// Because of this we don't enable stickiness by default to support all environments.
+        /// Because of this we don't enable pinning by default to support all environments.
         #[serde(default)]
-        pub sticky_node_ports: bool,
+        pub pinning_node_ports: bool,
     }
 }