DreadfullyDistinct commented on issue #16881:
URL: https://github.com/apache/airflow/issues/16881#issuecomment-972671589
Hi,
so our case was also related to service account permissions. We have now
following permissions configured for service account, which works now fine for
scheduler detecting already running pods before restart.
```
resources:
- pods
verbs:
- get
- create
- list
- delete
- patch
```
Thanks @dberzano for suggestion. if anyone sees the issue again, I guess you
need to check if you get some "Resource: Forbidden" Errors on scheduler logs to
see if you have a permission missing, to adopt a pod that was running before
scheduler start.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
