Bash- commented on issue #14872: URL: https://github.com/apache/airflow/issues/14872#issuecomment-988666630
@potiuk Clear, I understand what you mean. And you are right, we now understand that the user is created in the backend database, we did not clear it when uninstalling the Helm deployment, installing the Helm Chart again used the old database records. We did this because we are looking for a way to programmatically create a user. Some context about how we hoped to do it: 1. We use [Secret Store CSI Driver](https://secrets-store-csi-driver.sigs.k8s.io/introduction.html) to load Azure Key Vault secrets as Kubernetes Secrets into our AKS cluster. We can use those k8s secrets in our `values.yml` for fields like `resultBackendSecretName` or `fernetKeySecretName`. 2. We hoped to store user credentials like this as well, and have an option in the `values.yml` to create users based on values that are stored in a Kubernetes secret. That is why we tried some different things, like misusing the defaultuser value. Since this is not the way to go, could you advise us how we should create users within Airflow on Kubernetes? Should we maybe just do it manually via the UI or via the CLI with `airflow users create`? Or do you think we could still do that programmatically within our Airflow image? -- 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]
