[
https://issues.apache.org/jira/browse/AIRFLOW-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955382#comment-16955382
]
ASF subversion and git services commented on AIRFLOW-5223:
----------------------------------------------------------
Commit feef844e7d6cf77d76f17d11b5b5d517cba8fc0b in airflow's branch
refs/heads/v1-10-test from Gerardo Curiel
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=feef844 ]
[AIRFLOW-5223] Use kind for Kubernetes in CI (#5837)
This PR reimplements Kubernetes integration testing using kind,
a tool for running local Kubernetes clusters using Docker container
"nodes". The "nodes" are deployed to a separate docker daemon
(dind) started through docker-compose.
(cherry picked from commit e62056b2254e1447e20179f8d2911a93462cddc5)
> Use KinD for Kubernetes in CI
> -----------------------------
>
> Key: AIRFLOW-5223
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5223
> Project: Apache Airflow
> Issue Type: Improvement
> Components: ci
> Affects Versions: 1.10.4
> Reporter: Gerardo Curiel
> Priority: Minor
> Fix For: 2.0.0
>
>
> This PR reimplements Kubernetes integration testing using kind, a tool for
> running local Kubernetes clusters using Docker container "nodes". The "nodes"
> are deployed inside the main airflow-testing container, so I needed to also
> install docker, hence, this particular implementation relies on
> docker-in-docker.
> For completeness sake, I considered mounting the host's /var/run/docker.sock
> socket so that we could rely on the host's Docker daemon instead of running
> docker-in-docker, but I felt docker-in-docker, being a more self-contained
> implementation, offers the least amount of friction when using it locally for
> development purposes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
