-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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.
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
Kubernetes on host #8265
Kubernetes on host #8265
Conversation
Hey @dimberman @kaxil @turbaszek -> I have almost working change where Kind Kubernetes cluster is created on the host side and it can be used to run the tests with Kubernetes. I nicely integrated it with breeze so that you can run:
and then you should be able to run tests. I just wanted to share it with you so that you can take a look. This can be very easily reused for the helm chart deployments (@dimbermann) and I think it's a better way of handling Kind Setup than relying in Github Action specific configuration from #8222 - because it can be run for local testing as well and it can be run on any CI (Travis/GA/Cloud Build. ....) . I updated the documentation including explanation how I imagine running the tests locally with breeze. I am planning to complete it tomorrow - but please take a look in the meantime :). It is based on the #8261 so only look at the latest commit. |
cf2f550
to
c18a829
Compare
@potiuk is there a reason we're still defaulting to such an old k8s? We should set it to at least 1.17 (unless that should be a separate PR). |
@dimberman Old release? Version 1.14 is the latest version of the stable release channel on GKE. Version 1.15 is the latest version of the regular release channel. I don't think we need to use the latest possible version, but the most popular version. |
The following Kubernetes versions are currently available for new clusters in Amazon EKS:
https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html You can use the newer version if you use GKE on AWS. However, this is a new service that was released yesterday. |
No reason whatsoever. Just carried from the past. Right now it's as easy as modifying a few constants :) |
c18a829
to
65d597c
Compare
65d597c
to
da8a050
Compare
7d30b1b
to
9ca8192
Compare
e9f88b4
to
2088d81
Compare
2088d81
to
f960abb
Compare
@mik-laj - for now the deployment we have is kinda "abomination" - we will replace it with helm charts shortly - for now I know the Deployments we have won't work for higher versions of Kubernetes but I do not want to lose time trying to fix them since we are going to swap them with the helm charts. |
Nice work @potiuk |
@potiuk I think this may be causing the
I've also experienced it causing the command to hang indefinitely. |
#TODO FIXME | ||
if [[ "${INTEGRATIONS[*]}" == *"kubernetes"* ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm @potiuk ? I get ./breeze: line 382: INTEGRATIONS[*]: unbound variable
when starting ./breeze
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, Mac OS thingie. I used to catch it early before I switched to Linux. Fixed in #9135
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @potiuk !
Oh did not read that @jhtimmins - same for me. |
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)
We upgraded to v2 in apache#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it.
We upgraded to v2 in #8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it.
We upgraded to v2 in apache#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it.
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)
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)
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)
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
We upgraded to v2 in apache/airflow#8265 for other places in `.github/workflows/ci.yml`. This was left, so fixing it. GitOrigin-RevId: a38c35a47f542bb480e331bf78d19ee612aa5041
Make sure to mark the boxes below before creating PR: [x]
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.