minnieshi commented on issue #28637:
URL: https://github.com/apache/airflow/issues/28637#issuecomment-2435113381
After I used ChatGPT, I started getting more elaborate answers. And I can
now understand that the issue that I reported was not an issue
Here are the answers to the questions about the `behavior of Kubernetes
jobs`.
```
By default, a Kubernetes Job (like migrate-database) does not automatically
rerun during Helm upgrades or FluxCD reconciliations unless a specific Helm
hook (e.g., pre-upgrade, post-install, etc.) is attached to the Job.
If you want the Job to run on upgrades (e.g., when upgrading Airflow
versions or configurations that require schema changes), you must use the
pre-upgrade or another appropriate hook to force the Job to run again.
```
The reason for the behavior that I reported was that _I did not use the hook
to ask for the JOBS to run for any changes_ like 'AIRFLOW__CORE__LOAD_EXAMPLES'
from true to false
If i wanted the job to run for any changes, It should have been:
```
createUserJob:
useHelmHooks: true
annotations:
"helm.sh/hook": "pre-upgrade, post-install"
```
but it was:
```
createUserJob:
useHelmHooks: false
migrateDatabaseJob:
useHelmHooks: false
```
--
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]
