Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move Kubernetes tests and kind setup out of the container to host #8782

Closed
potiuk opened this issue May 8, 2020 · 0 comments
Closed

Move Kubernetes tests and kind setup out of the container to host #8782

potiuk opened this issue May 8, 2020 · 0 comments
Labels
area:CI Airflow's tests and continious integration area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code area:dev-tools kind:feature Feature Requests
Milestone
Airflow 1.10.11

Comments

@potiuk
Copy link
Member

potiuk commented May 8, 2020

Description

We should move kind setup out of the container for CI to the host environment

Use case / motivation

Makes CI image smaller and setup easier for local testing.
@potiuk potiuk added area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code area:dev-tools kind:feature Feature Requests area:CI Airflow's tests and continious integration labels May 8, 2020
@potiuk potiuk mentioned this issue May 8, 2020
Closed
8 tasks
@potiuk potiuk added this to the Airflow 1.10.11 milestone Jun 1, 2020
potiuk added a commit to PolideaInternal/airflow that referenced this issue Jun 3, 2020
@potiuk
Kubernetes Cluster is started on host not in the container
b7ab2df 
Tests requiring Kubernetes Cluster are now moved out of
the regular CI tests and moved to "kubernetes_tests" folder
so that they can be run entirely on host without having
the CI image built at all. They use production image
to run the tests on KinD cluster and we add tooling
to start/stop/deploy the application to the KinD cluster
automatically - for both CI testing and local development.

This is a pre-requisite to convert the tests to convert the
tests to use the official Helm Chart and Docker images or
Apache Airflow.

It closes apache#8782
@potiuk potiuk closed this as completed in ff5dccc Jun 3, 2020
potiuk added a commit that referenced this issue Jun 9, 2020
@potiuk
Kubernetes Cluster is started on host not in the container (#8265)
8dacc27 
Tests requiring Kubernetes Cluster are now moved out of
the regular CI tests and moved to "kubernetes_tests" folder
so that they can be run entirely on host without having
the CI image built at all. They use production image
to run the tests on KinD cluster and we add tooling
to start/stop/deploy the application to the KinD cluster
automatically - for both CI testing and local development.

This is a pre-requisite to convert the tests to convert the
tests to use the official Helm Chart and Docker images or
Apache Airflow.

It closes #8782

(cherry picked from commit ff5dccc)
potiuk added a commit that referenced this issue Jun 29, 2020
@potiuk
Kubernetes Cluster is started on host not in the container (#8265)
3c20d6f 
Tests requiring Kubernetes Cluster are now moved out of
the regular CI tests and moved to "kubernetes_tests" folder
so that they can be run entirely on host without having
the CI image built at all. They use production image
to run the tests on KinD cluster and we add tooling
to start/stop/deploy the application to the KinD cluster
automatically - for both CI testing and local development.

This is a pre-requisite to convert the tests to convert the
tests to use the official Helm Chart and Docker images or
Apache Airflow.

It closes #8782

(cherry picked from commit ff5dccc)
kaxil pushed a commit that referenced this issue Jul 1, 2020
@potiuk @kaxil
Kubernetes Cluster is started on host not in the container (#8265)
32ed3c6 
Tests requiring Kubernetes Cluster are now moved out of
the regular CI tests and moved to "kubernetes_tests" folder
so that they can be run entirely on host without having
the CI image built at all. They use production image
to run the tests on KinD cluster and we add tooling
to start/stop/deploy the application to the KinD cluster
automatically - for both CI testing and local development.

This is a pre-requisite to convert the tests to convert the
tests to use the official Helm Chart and Docker images or
Apache Airflow.

It closes #8782

(cherry picked from commit ff5dccc)
cfei18 pushed a commit to cfei18/incubator-airflow that referenced this issue Mar 5, 2021
@potiuk
Kubernetes Cluster is started on host not in the container (apache#8265)
8397e60 
Tests requiring Kubernetes Cluster are now moved out of
the regular CI tests and moved to "kubernetes_tests" folder
so that they can be run entirely on host without having
the CI image built at all. They use production image
to run the tests on KinD cluster and we add tooling
to start/stop/deploy the application to the KinD cluster
automatically - for both CI testing and local development.

This is a pre-requisite to convert the tests to convert the
tests to use the official Helm Chart and Docker images or
Apache Airflow.

It closes apache#8782

(cherry picked from commit ff5dccc)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:CI Airflow's tests and continious integration area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code area:dev-tools kind:feature Feature Requests
Projects
None yet
Milestone
Airflow 1.10.11
Development

No branches or pull requests
1 participant
@potiuk