You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is missing?
Currently, there is no way to specify nodeSelector labels for the crd-upgrader-job-k8ssandra job, which means the job can run on nodes that are not compatible with the k8ssandra/k8ssandra-tools container (e.g., ARM64 nodes).
Why do we need it?
Adding support for nodeSelector would allow users to specify which nodes this job can run on, offering a workaround for the ARM64 compatibility issue. This ensures that the job only runs on compatible nodes.
Environment
K8ssandra Operator version:
v1.9.0
* Kubernetes Cluster:Mixed-architecture cluster with ARM64 and AMD64 nodes.
Anything else we need to know?:
This feature will provide users more control
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-68
The text was updated successfully, but these errors were encountered:
What is missing?
Currently, there is no way to specify nodeSelector labels for the crd-upgrader-job-k8ssandra job, which means the job can run on nodes that are not compatible with the k8ssandra/k8ssandra-tools container (e.g., ARM64 nodes).
Why do we need it?
Adding support for nodeSelector would allow users to specify which nodes this job can run on, offering a workaround for the ARM64 compatibility issue. This ensures that the job only runs on compatible nodes.
Environment
K8ssandra Operator version:
* Kubernetes Cluster:Mixed-architecture cluster with ARM64 and AMD64 nodes.v1.9.0
Anything else we need to know?:
This feature will provide users more control
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-68
The text was updated successfully, but these errors were encountered: