dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-422982154
@odracci I like your solution better as a short-term fix (switching to k-d-c
should ideally be done later when the
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-420793289
@Fokko @bolkedebruin @ashb I am seeing multiple errors with the kubernetes
executor once running:
1. The API
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-420438891
@Fokko @barni is going to investigate how we can make the airflow API tests
to work today. Should hopefully have this
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417791464
@gerardo ok further process. The main issue left is that it keeps attempting
to compile the s3 tests even though there
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417545995
@gerardo Ok it's now solidly back in the court of "getting TOX to work".
Kubeadm is able to build and deploy. PTAL and
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417541379
cc: @feng-tao @kaxil just a warning any PR merged right now is not being
tested against kubernetes.
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417538581
@Fokko @bolkedebruin @gerardo I was able to get kubeadm to work with a local
registry (that was a rough experience
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417466718
@gerardo I agree that it would be a pain, but it's going to REALLY hurt if
we merge PRs for a couple of weeks and then
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417349648
@Fokko @gerardo Quick update. I've been still running into weird minikube
issues and have been unable to get the CI to
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-417026819
@gerardo Minikube definitely will not run inside docker (there's such thing
as "docker in docker" but it's a really bad
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-415696995
@gerardo No luck with that. Any other potential culprits?
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-415601935
dimberman commented on issue #3797: [AIRFLOW-2952] Splits CI into k8s +
docker-compose
URL:
https://github.com/apache/incubator-airflow/pull/3797#issuecomment-415597921
@bolkedebruin @Fokko @kaxil PTAL. I'm going to try to get this all working
tonight (though I assume the tests should
13 matches
Mail list logo
