jsnb-devoted opened a new issue, #53198:
URL: https://github.com/apache/airflow/issues/53198

   ### Official Helm Chart version
   
   1.17.0 (latest released)
   
   ### Apache Airflow version
   
   3
   
   ### Kubernetes Version
   
   v1.32.5-eks-5d4a308
   
   ### Helm Chart configuration
   
   Moving to airflow 3 I removed the `webserver` from my values file and I 
noticed the helm deploy creating the create-user `Job` 
(https://github.com/apache/airflow/blob/main/chart/templates/jobs/create-user-job.yaml#L23C1-L24C1).
 
   
   I don't know enough about the job to know but it seemed like either that 
defaultUser config needs to be migrated to the apiServer section if its still 
relevant.
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   Running the helm deploy tried to create a `Job` that I had never seen before 
because we always had this in our values file:
   ```
     webserver:
       defaultUser:
         enabled: false
   ```
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   Upgrade the chart airflowVersion to airflow 3, remove the `webserver` 
section and do a helm deploy.
   
   
   
   ### Anything else
   
   Adding this back in the values unblocks me:
   ```
     webserver:
       defaultUser:
         enabled: false
   ```
   
   but wanted to raise it in case it wasn't intentional.
   
   Also maybe I am supposed to keep some `webserver` values in the values file? 
I assumed that it was safe to wipe out because that is no longer a component of 
airflow 3.
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to