You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2019/10/20 04:35:00 UTC
[jira] [Resolved] (AIRFLOW-5223) Use KinD for Kubernetes in CI
[ https://issues.apache.org/jira/browse/AIRFLOW-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Potiuk resolved AIRFLOW-5223.
-----------------------------------
Fix Version/s: (was: 2.0.0)
1.10.7
Resolution: Fixed
> 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: 1.10.7
>
>
> 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)