Well locally I do this (which I'm hoping to PR soon once tests are
passing): https://github.com/apache/incubator-airflow/pull/4326. This
allows me to connect to any k8s cluster.
But for simplicity/parity with CI, you can follow these steps:
This will give you airflow runniung on minikube. you can then do a kubectl
port-forward <airflow container> 8080 8080 to port-forward into the
I can attempt to check webserver logs again when I have some time
(hopefully this weekend/next week) as well.
On Tue, Dec 18, 2018 at 3:15 PM Tao Feng <fengtao04@xxxxxxxxx> wrote:
I assume so. How do you run your test? I could try it on my side and see if
I could reproduce the problem.
On Tue, Dec 18, 2018 at 2:17 PM Daniel Imberman <danielryan2430@xxxxxxxxx>
Do we need to install NPM? Should I add npm to the docker image/bootstrap
On Tue, Dec 18, 2018 at 1:20 PM Tao Feng <fengtao04@xxxxxxxxx> wrote:
I just try with latest master which could show the dag after login as
Admin. One last check: have you done the `npm install` and `npm run
On Tue, Dec 18, 2018 at 12:50 PM Daniel Imberman <
I believe I am using the new UI since I have to login as admin to get
can still see certain admin panels, but the primary DAG one doesn't
any DAGs even when I explicitly put one in the folder.
On Tue, Dec 18, 2018, 12:26 PM Tao Feng <fengtao04@xxxxxxxxx wrote:
Are you using the Old UI or the new UI? Do you login as Admin user
On Tue, Dec 18, 2018 at 11:56 AM Daniel Imberman <
I've been testing the K8sExecutor and I notice that when I open
unable to see any of the DAGs even though they are in the
folder. I'm also still able to launch DAGs via the API. I have
this on any of the other executors yet. Is this a known issue?
the question on whether we can set up some form of UI testing
think the current unit/integration tests would catch this kind of