hussein-awala opened a new pull request, #33371:
URL: https://github.com/apache/airflow/pull/33371
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
This PR updates the labels used in `runs-on` to migrate the workflows to the
new GHA runners running on Airflow EKS cluster, and managed by an Actions
Runner Controller (ARC).
In the new cluster, we can choose between 3 different sizes for the self
hosted runners (the instance type could be change):
- small -> t4g-medium (2 cpus, 4Gb of ram) -> `runs-on: ${{
fromJson(needs.build-info.outputs.runs-on-small) }}`
- medium -> t4g-xlarge (4 cpus, 16Gb of ram) -> `runs-on: ${{
fromJson(needs.build-info.outputs.runs-on-medium) }}`
- large -> t4g-2xlarge (8 cpus, 32 Gb of ram) -> `runs-on: ${{
fromJson(needs.build-info.outputs.runs-on-large) }}`
And we can add new runner sets with different characteristics in the future,
for ex create a specific docker image which contains some pre-installed
packages and use it in specific jobs, or maybe create a new runner image from
Airflow CI image and update it via the CI after updating the breeze or Airflow
dependencies. (to be discussed later).
Also, this PR removes all the steps which setup python using
`actions/setup-python@v4`, because of a bug in the action
(actions/setup-python#705). As a workaround, I pre-installed python in the
runner docker image, we can revert this change after fixing the bug, or keep it
based on the performance of the runner.
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
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
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
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: commits-unsubscr...@airflow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
