snjypl commented on PR #29012: URL: https://github.com/apache/airflow/pull/29012#issuecomment-1398479900
> apiVersion: rbac.authorization.k8s.io/v1 > kind: RoleBinding > metadata: > annotations: > meta.helm.sh/release-name: airflowlocal > meta.helm.sh/release-namespace: airflow > creationTimestamp: "2023-01-18T09:52:13Z" > labels: > app.kubernetes.io/managed-by: Helm > chart: airflow-1.7.0 > heritage: Helm > release: airflowlocal > tier: airflow > name: airflowlocal-pod-launcher-rolebinding > namespace: airflow > resourceVersion: "13279" > uid: 05617ca4-ebf3-424a-990b-8b59274702f0 > roleRef: > apiGroup: rbac.authorization.k8s.io > kind: Role > name: airflowlocal-pod-launcher-role > subjects: > - kind: ServiceAccount > name: airflowlocal-scheduler > namespace: airflow > - kind: ServiceAccount > name: airflowlocal-worker > namespace: airflow @arjunanan6 it seems like you have not applied the patch in this PR correctly, as you can see `airflowlocal-webserver` service account does not have pod laucher role. you can try to manually apply the bellow gist https://gist.github.com/snjypl/aeebe582be0190e483163224f9c966e7 reason why the scheduled task are not having issue is, the scheduled task pod are launched by the `scheduler`. the scheduler sa has pod launcher role. in case of manual trigger, the k8s pod is launched by the `webserver`. how are you deploying the helm chart from this PR? if you can share the steps i might be able to help you with it. anyway, manually doing a `kubectl apply -f <the gist file>` should fix it for you. later you can try testing the helm chart. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
