<h3 dir="auto">Official Helm Chart version</h3>
<p dir="auto">1.1.0 (latest released)</p>
<h3 dir="auto">Apache Airflow version</h3>
<p dir="auto">2.1.2</p>
<h3 dir="auto">Kubernetes Version</h3>
<p dir="auto">1.18</p>
<h3 dir="auto">Helm Chart configuration</h3>
<p dir="auto">no configuration</p>
<h3 dir="auto">Docker Image customisations</h3>
<p dir="auto">no customization</p>
<h3 dir="auto">What happened</h3>
<p dir="auto">if we install airflow against argoCD, argoCD synchronizes all, then webserver and scheduler tries to run, inits with the wait-for-migrations but the job from migrate-database-job.yaml will never run because is not yet "installed" from the point of view of argoCD synchronization.</p>
<h3 dir="auto">What you expected to happen</h3>
<p dir="auto">To run the job from migrate-database-job.yaml without need of post-install in first "installation"</p>
<h3 dir="auto">How to reproduce</h3>
<p dir="auto">Install chart using argoCD (per example version v1.8.7+eb3d1fb)</p>
<h3 dir="auto">Anything else</h3>
<p dir="auto">We can fix it setting replicas to 0 to scheduler and webserver (minimum), then we let to continue to post-install and then change again the replicas to scheduler and webserver</p>
<h3 dir="auto">Are you willing to submit PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> Yes I am willing to submit a PR!</li>
</ul>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>
<h3 dir="auto">Apache Airflow version</h3>
<p dir="auto">2.2.0 (latest released)</p>
<h3 dir="auto">Operating System</h3>
<p dir="auto">Ubuntu 20.04.2 LTS</p>
<h3 dir="auto">Versions of Apache Airflow Providers</h3>
<p dir="auto">docker tag: apache/airflow:2.2.0-python3.7</p>
<h3 dir="auto">Deployment</h3>
<p dir="auto">Other</p>
<h3 dir="auto">Deployment details</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">What happened</h3>
<p dir="auto">No matter what time zone do I specify in config file [core/default_timezone] or dag's start date, the suffix of dag_run_id is always "+00:00".</p>
<h3 dir="auto">What you expected to happen</h3>
<p dir="auto">The time zone suffix of dag_run_id should be some kind related to the time zone that I specify in the config file or the dag object. Is there any way to customize the format of dag_run_id?</p>
<h3 dir="auto">How to reproduce</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Anything else</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Are you willing to submit PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> Yes I am willing to submit a PR!</li>
</ul>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>