Hi! I'm having trouble understanding what's supposed to happen with k8s pod specs in Flyte. I have a default-node-selector set like so:

configmap:
...
  k8s:
    plugins:
      k8s:
...
        default-node-selector:
          algorithm-node: "true"
          "<http://cloud.google.com/gke-smt-disabled|cloud.google.com/gke-smt-disabled>": "false"

but in my pod task, I add a V1PodSpec with a different node-selector

@task(task_config=Pod(pod_spec=V1PodSpec(
        node_selector={
            "large-ssd-node": "true",
            "<http://cloud.google.com/gke-large-ssd|cloud.google.com/gke-large-ssd>": "true",
        },
...)
def mytask():

However, when I look at the yaml that ultimately gets generated, it seems to be a merge of the two different node-selectors

nodeSelector:
    algorithm-node: "true"
    <http://cloud.google.com/gke-large-ssd|cloud.google.com/gke-large-ssd>: "true"
    <http://cloud.google.com/gke-smt-disabled|cloud.google.com/gke-smt-disabled>: "false"
    large-ssd-node: "true"

Is this expected behavior? If so, is there a way to replace the default-node-selector, so I only end up with

nodeSelector:
    <http://cloud.google.com/gke-large-ssd|cloud.google.com/gke-large-ssd>: "true"
    large-ssd-node: "true"

we are looking into this.

Thanks, @thankful-minister-83577. Yeah, all tasks were in the same namespace. I'll create an issue now.