GitHub user potiuk added a comment to the discussion: How to create custom roles when deploying airflow with helm chart
Generally speaking helm is for installing apps not intializing the database with custom roles variables, connections etc., you should have additional synchronization and configuraiton scripts that are not part of "helm install" - that woudl be best way and you are free to do it as you want - but outside of Helm. We have `airflow roles export/import` and `airflow users export/import` tools for that - but generally it's something that is independent from "application" installation that helm provides. If you wish to run it initialization script and init container, you need to do it in a way that will handle all ambiguities - i.e. what happens when you create or update roles in the future, how to delete those that were deleted/added, how not to override the roles that were created manually - and also handle the case that the init container is executed every time the main container starts (which means tha this init container will run many times even if you do not re-deploy helm - basically any time your containers start. in your case yes - you miss all the environment variables that oother containers had - so your "airflow" command is not using the right credentials - you can look at the definition of those containers you have via `helm install --dry-run` for example. GitHub link: https://github.com/apache/airflow/discussions/45543#discussioncomment-11796297 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
