Comment 5 for bug 1993716

Here is the example of the kubeflow-dashboard-operator that ends up on a GPU node (las2-mlgpu43).
The application is specified in the bundle as follows:
  kubeflow-dashboard:
    charm: kubeflow-dashboard
    channel: 1.6/stable
    scale: 1
    _github_repo_name: kubeflow-dashboard-operator
    constraints: tags=node.mldatanode=true,^node.mlgpunode=true

$ kubectl get statefulsets.apps -n kubeflow kubeflow-dashboard-operator -o json | jq .spec.template.spec.affinity
null

Here is the full YAML for the kubeflow-dashboard-operator statefulset: https://pastebin.canonical.com/p/RGb2YyzRr3/
Here is the full JSON for the kubeflow-dashboard-operator statefulset: https://pastebin.canonical.com/p/Y6pYgHxQzD/

The cluster has the following nodes:
NAME STATUS ROLES AGE VERSION
las2-mlgpu41 Ready <none> 29d v1.24.3
las2-mlgpu43 Ready <none> 28d v1.24.3
lv01-mlkfwapp-l01 Ready <none> 34d v1.24.6
lv01-mlkfwapp-l02 Ready <none> 34d v1.24.6
lv01-mlkfwapp-l03 Ready <none> 34d v1.24.6
lv01-mlkfwapp-l04 Ready <none> 34d v1.24.6
lv01-mlkfwapp-l05 Ready <none> 34d v1.24.6
lv1-mlksapp-l01 Ready control-plane,master 35d v1.24.6
lv1-mlksapp-l02 Ready control-plane,master 35d v1.24.6
lv1-mlksapp-l03 Ready control-plane,master 35d v1.24.6
lv1-mlksapp-l04 Ready control-plane,master 35d v1.24.6
lv1-mlksapp-l05 Ready control-plane,master 35d v1.24.6

Here is the full YAML for the nodes in the cluster: https://pastebin.canonical.com/p/gjqR2hnjYh/
Here is the full JSON for the nodes in the cluster: https://pastebin.canonical.com/p/R8PKD3DBPq/