potiuk commented on issue #21943: URL: https://github.com/apache/airflow/issues/21943#issuecomment-1475948017
Note that this fix has not yet been released and requires manual patching and recreating your deployment from scratch. Is `ttlSecondsAfterFinished` part of your job definition @jay-olulana ? (https://github.com/apache/airflow/pull/29314/files)? Can you double check it? In order to use it, you will have to either use main version of the chart or apply the change manually to your chart and only after that deploy your chart (with the changeS) from the scratch. And your k8s version would have to support ttlSecondsAfterFinished. Only then any NEXT upgrade (assuming it is done later than the `ttlSecondsAfterFinished` seconds after the job finishes) should work. Simply K8S would automatically delete the completed job after this time if everything aligns. So you need to make sure that your chart contains the changes, that your job gets the spec parameter and that k8s handles it. If those conditions are not fulfilled you can always redeploy Airflow from the scratch. -- 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]
