[helm] Isolate defaultUser handling in createUserJob

[nhuantho]

What:

• When I read #53198 and then checked the {release-name}-create-user-job, I saw that it is used only to create a user via the airflow users command (FAB CLI Commands). Therefore, I believe that defaultUser should not be part of the webserver or apiServer.
• From my perspective, we should decouple the responsibilities of each service. Currently, createUserJob depends on the webserver, but the webserver has been replaced by the apiServer. As a result, we should move defaultUser to the apiServer configuration.

Solution:

• Move defaultUser into createUserJob to isolate the functionality of createUserJob.
• Remove the usage of webserver.defaultUser from the Helm chart and related tests.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[nhuantho]

I cleaned the fork branch, so it affected to close pr:59715, so I created an alternative pr.

[Charlesfox1]

Hi there - the default values of the latest Helm chart version (1.18) still reference defaultUser under webserver:

Helm Chart link.

Is that planned to change in the next version of the Apache Airflow Helm chart?

I'm trying to deploy v1.18 with modified admin user credentials. Thanks so much, sorry if answer is obvious.

[jscheffl]

Is that planned to change in the next version of the Apache Airflow Helm chart?

I'm trying to deploy v1.18 with modified admin user credentials. Thanks so much, sorry if answer is obvious.

Yes, see this PR. You can wait until (pending/overduw) 1.19 release of the helm chart or pull it from main which includes this here.