hey folks, I am having an issue with the k8s run l...
# ask-community
h
hey folks, I am having an issue with the k8s run launcher config that I could use some help with. So the issue is that when Dagster launches jobs, it isn't picking the right node pool. I am adding a runK8sConfig section to my run launcher config but its violating the schema check when I try to helm apply. Helm Error:
runLauncher.config.k8sRunLauncher: Additional property runK8sConfig is not allowed
Config:
Copy code
"runK8sConfig": {
   "containerConfig": null,
   "jobMetadata": null,
   "jobSpecConfig": null,
   "podSpecConfig": {
      "nodeSelector": {
         "<http://cloud.google.com/gke-nodepool|cloud.google.com/gke-nodepool>": "airflow-ha-pool-2"
      },
      "tolerations": [
         {
            "effect": "NoSchedule",
            "key": "dedicated",
            "operator": "Equal",
            "value": "airflow-ha"
         }
      ]
   },
   "podTemplateSpecMetadata": null
}
which is under
runLauncher
->
config
->
k8sRunLauncher
any advice here?
r
runK8sConfig
was added recently in
1.1.8
- you should make sure that you’re installing from the correct helm chart:
Copy code
helm repo search dagster
to update your index, you should update your helm repos:
Copy code
helm repo update
h
awesome thanks! we just caught it to!