<h3 dir="auto">Describe the issue with documentation</h3>
<p dir="auto">On <a href="https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/patch_dag" rel="nofollow">https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#operation/patch_dag</a><br>
the payload in the example for PATCH  /dags/{dag_id} suggest that it's possible to update <code class="notranslate">schedule_interval</code> which is not true :</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="{
&quot;is_paused&quot;: true,
&quot;schedule_interval&quot;: {
&quot;__type&quot;: &quot;string&quot;,
&quot;days&quot;: 0,
&quot;seconds&quot;: 0,
&quot;microseconds&quot;: 0
}
}"><pre class="notranslate"><code class="notranslate">{
"is_paused": true,
"schedule_interval": {
"__type": "string",
"days": 0,
"seconds": 0,
"microseconds": 0
}
}
</code></pre></div>
<h3 dir="auto">How to solve the problem</h3>
<p dir="auto">Update documentation removing the <code class="notranslate">schedule_interval</code> part from payload</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>
<p dir="auto"><strong>Description</strong></p>
<p dir="auto">Since Airflow 2 we get a lot of customization options for pods spawned using <code class="notranslate">KubernetesPodOperator</code>. There is, however, one area in which nothing has changed and it's <code class="notranslate">xcom_sidecar_container</code>. Currently, all of the specs for it are hardcoded in <code class="notranslate">PodDefaults</code> class.</p>
<p dir="auto">This issue is meant to start discussion and to possibly shape the end solution enabling configuration of xcom side container (unless there is a feeling it's not needed).</p>
<p dir="auto"><strong>Use case / motivation</strong></p>
<p dir="auto">We are running on self-hosted k8s with own docker repository (JFrog artifactory) and in our current setup we are required to spawn pods using full path to the repo - we cannot do <code class="notranslate">docker pull alpine</code> but need to do <code class="notranslate">docker pull arficatory.domain/registry/alpine</code>.</p>
<p dir="auto"><strong>Are you willing to submit a PR?</strong></p>
<p dir="auto">Yes, but could use some points, discussion on what would be the acceptable target solution.</p>
<p dir="auto"><strong>Related Issues</strong></p>
<p dir="auto">n/a</p>