+1
On Fri, Sep 13, 2019 at 8:40 PM Jarek Potiuk wrote:
>
> +1 for aieflow-on-k8s-operator. Good enough :)
>
> J.
>
> pt., 13 wrz 2019, 19:19 użytkownik Tao Feng napisał:
>
> > +1 on `airflow-on-k8s-operator` as well
> >
> > On Fri, Sep 13, 2019 at 10:07 AM Ry Walker wrote:
> >
> > > +1 from me
+1 for aieflow-on-k8s-operator. Good enough :)
J.
pt., 13 wrz 2019, 19:19 użytkownik Tao Feng napisał:
> +1 on `airflow-on-k8s-operator` as well
>
> On Fri, Sep 13, 2019 at 10:07 AM Ry Walker wrote:
>
> > +1 from me for sure. Thanks for pushing this through Aizhamal.
> >
> > GCP just named the
+1 on `airflow-on-k8s-operator` as well
On Fri, Sep 13, 2019 at 10:07 AM Ry Walker wrote:
> +1 from me for sure. Thanks for pushing this through Aizhamal.
>
> GCP just named their flink operator (
> https://github.com/GoogleCloudPlatform/flink-on-k8s-operator
> ) *flink-on-k8s-operator.*
>
> So
+1 from me for sure. Thanks for pushing this through Aizhamal.
GCP just named their flink operator (
https://github.com/GoogleCloudPlatform/flink-on-k8s-operator )
*flink-on-k8s-operator.*
So for name, I prefer either *k8s-operator-for-airflow* or
*airflow-on-k8s-operator*. I sort of like the
Hi John,
I've never tried it like you're suggesting. It feels a bit risky. I can't
tell what you will encounter if you run different versions of Airflow. How
are you running Airflow?
Cheers, Fokko
Op do 12 sep. 2019 om 20:29 schreef John Smodic :
> Hey all,
>
> I'm looking to find an upgrade pa
