From c2de62be772143d97f44d7418764b8dd50c8acc6 Mon Sep 17 00:00:00 2001 From: wangxy518 <40482095+wangxy518@users.noreply.github.com> Date: Thu, 27 Aug 2020 09:06:41 +0800 Subject: [PATCH] Update 2018-06-28-Airflow-Kubernetes-Operator.md --- .../zh/blog/_posts/2018-06-28-Airflow-Kubernetes-Operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/zh/blog/_posts/2018-06-28-Airflow-Kubernetes-Operator.md b/content/zh/blog/_posts/2018-06-28-Airflow-Kubernetes-Operator.md index 86c0fd1ae3..5606cf9c2c 100644 --- a/content/zh/blog/_posts/2018-06-28-Airflow-Kubernetes-Operator.md +++ b/content/zh/blog/_posts/2018-06-28-Airflow-Kubernetes-Operator.md @@ -615,7 +615,7 @@ kubectl cp /:/root/airflow/dags -c scheduler -This feature is just the beginning of multiple major efforts to improves Apache Airflow integration into Kubernetes. The Kubernetes Operator has been merged into the 1.10 release branch of Airflow (the executor in experimental mode), along with a fully k8s native scheduler called the Kubernetes Executor (article to come). These features are still in a stage where early adopters/contributers can have a huge influence on the future of these features. +This feature is just the beginning of multiple major efforts to improves Apache Airflow integration into Kubernetes. The Kubernetes Operator has been merged into the 1.10 release branch of Airflow (the executor in experimental mode), along with a fully k8s native scheduler called the Kubernetes Executor (article to come). These features are still in a stage where early adopters/contributors can have a huge influence on the future of these features.