This is an automated email from the ASF dual-hosted git repository.
fhueske pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit e165b5ec467ebd927599340e7d0c625cb48750c6
Author: Fabian Hueske <fhue...@apache.org>
AuthorDate: Mon Jan 20 13:46:37 2020 +0100
Rebuild website
---
content/blog/feed.xml | 14 +++++++-------
content/news/2019/12/09/flink-kubernetes-kudo.html | 14 +++++++-------
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 2fe71fe..742368a 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -378,7 +378,7 @@ To understand why this is the case, let us start with
articulating a realistic s
<p>Install the <code>kubectl</code> CLI tool. The KUDO CLI
is a plugin for the Kubernetes CLI. The official instructions for installing
and setting up kubectl are <a
href="https://kubernetes.io/docs/tasks/tools/install-kubectl/">here</a>.</p>
-<p>Next, let’s install the KUDO CLI. At the time of this writing, the
latest KUDO version is v0.8.0. You can find the CLI binaries for download <a
href="https://github.com/kudobuilder/kudo/releases">here</a>.
Download the <code>kubectl-kudo</code> binary for your OS and
architecture.</p>
+<p>Next, let’s install the KUDO CLI. At the time of this writing, the
latest KUDO version is v0.10.0. You can find the CLI binaries for download
<a
href="https://github.com/kudobuilder/kudo/releases">here</a>.
Download the <code>kubectl-kudo</code> binary for your OS and
architecture.</p>
<p>If you’re using Homebrew on MacOS, you can install the CLI
via:</p>
@@ -396,15 +396,15 @@ $KUDO_HOME has been configured at /Users/gerred/.kudo
<p>The KUDO CLI leverages the kubectl plugin system, which gives you all
its functionality under <code>kubectl kudo</code>. This is a
convenient way to install and deal with your KUDO Operators. For our demo, we
use Kafka and Flink which depend on ZooKeeper. To make the ZooKeeper Operator
available on the cluster, run:</p>
-<div class="highlight"><pre><code>$ kubectl kudo
install zookeeper --version=0.2.0 --skip-instance
+<div class="highlight"><pre><code>$ kubectl kudo
install zookeeper --version=0.3.0 --skip-instance
</code></pre></div>
<p>The –skip-instance flag skips the creation of a ZooKeeper instance.
The flink-demo Operator that we’re going to install below will create it as a
dependency instead. Now let’s make the Kafka and Flink Operators available the
same way:</p>
-<div class="highlight"><pre><code>$ kubectl kudo
install kafka --version=0.1.3 --skip-instance
+<div class="highlight"><pre><code>$ kubectl kudo
install kafka --version=1.2.0 --skip-instance
</code></pre></div>
-<div class="highlight"><pre><code>$ kubectl kudo
install flink --version=0.1.1 --skip-instance
+<div class="highlight"><pre><code>$ kubectl kudo
install flink --version=0.2.1 --skip-instance
</code></pre></div>
<p>This installs all the Operator versions needed for our demo.</p>
@@ -424,7 +424,7 @@ $KUDO_HOME has been configured at /Users/gerred/.kudo
<div class="highlight"><pre><code>$ cd operators
$ kubectl kudo install
repository/flink/docs/demo/financial-fraud/demo-operator --instance flink-demo
-instance.kudo.dev/v1alpha1/flink-demo created
+instance.kudo.dev/v1beta1/flink-demo created
</code></pre></div>
<p>This time we didn’t include the –skip-instance flag, so KUDO will
actually deploy all the components, including Flink, Kafka, and ZooKeeper. KUDO
orchestrates deployments and other lifecycle operations using <a
href="https://kudo.dev/docs/concepts.html#plan">plans</a>
that were defined by the Operator developer. Plans are similar to <a
href="https://en.wikipedia.org/wiki/Runbook">runbooks</a>
and encapsulate all the procedures required [...]
@@ -432,7 +432,7 @@ instance.kudo.dev/v1alpha1/flink-demo created
<div class="highlight"><pre><code>$ kubectl kudo
plan status --instance flink-demo
Plan(s) for "flink-demo" in namespace "default":
.
-└── flink-demo (Operator-Version: "flink-demo-0.1.1" Active-Plan:
"deploy")
+└── flink-demo (Operator-Version: "flink-demo-0.1.4" Active-Plan:
"deploy")
└── Plan deploy (serial strategy) [IN_PROGRESS]
├── Phase dependencies [IN_PROGRESS]
│ ├── Step zookeeper (COMPLETE)
@@ -451,7 +451,7 @@ Plan(s) for "flink-demo" in namespace
"default":
<div class="highlight"><pre><code>$ kubectl kudo
plan status --instance flink-demo-kafka
Plan(s) for "flink-demo-kafka" in namespace "default":
.
-└── flink-demo-kafka (Operator-Version: "kafka-0.1.3" Active-Plan:
"deploy")
+└── flink-demo-kafka (Operator-Version: "kafka-1.2.0" Active-Plan:
"deploy")
├── Plan deploy (serial strategy) [IN_PROGRESS]
│ └── Phase deploy-kafka [IN_PROGRESS]
│ └── Step deploy (IN_PROGRESS)
diff --git a/content/news/2019/12/09/flink-kubernetes-kudo.html
b/content/news/2019/12/09/flink-kubernetes-kudo.html
index 694c9bc..31a0498 100644
--- a/content/news/2019/12/09/flink-kubernetes-kudo.html
+++ b/content/news/2019/12/09/flink-kubernetes-kudo.html
@@ -215,7 +215,7 @@
<p>Install the <code>kubectl</code> CLI tool. The KUDO CLI is a plugin for the
Kubernetes CLI. The official instructions for installing and setting up kubectl
are <a
href="https://kubernetes.io/docs/tasks/tools/install-kubectl/";>here</a>.</p>
-<p>Next, let’s install the KUDO CLI. At the time of this writing, the latest
KUDO version is v0.8.0. You can find the CLI binaries for download <a
href="https://github.com/kudobuilder/kudo/releases";>here</a>. Download the
<code>kubectl-kudo</code> binary for your OS and architecture.</p>
+<p>Next, let’s install the KUDO CLI. At the time of this writing, the latest
KUDO version is v0.10.0. You can find the CLI binaries for download <a
href="https://github.com/kudobuilder/kudo/releases";>here</a>. Download the
<code>kubectl-kudo</code> binary for your OS and architecture.</p>
<p>If you’re using Homebrew on MacOS, you can install the CLI via:</p>
@@ -233,15 +233,15 @@ $KUDO_HOME has been configured at /Users/gerred/.kudo
<p>The KUDO CLI leverages the kubectl plugin system, which gives you all its
functionality under <code>kubectl kudo</code>. This is a convenient way to
install and deal with your KUDO Operators. For our demo, we use Kafka and Flink
which depend on ZooKeeper. To make the ZooKeeper Operator available on the
cluster, run:</p>
-<div class="highlight"><pre><code>$ kubectl kudo install zookeeper
--version=0.2.0 --skip-instance
+<div class="highlight"><pre><code>$ kubectl kudo install zookeeper
--version=0.3.0 --skip-instance
</code></pre></div>
<p>The –skip-instance flag skips the creation of a ZooKeeper instance. The
flink-demo Operator that we’re going to install below will create it as a
dependency instead. Now let’s make the Kafka and Flink Operators available the
same way:</p>
-<div class="highlight"><pre><code>$ kubectl kudo install kafka --version=0.1.3
--skip-instance
+<div class="highlight"><pre><code>$ kubectl kudo install kafka --version=1.2.0
--skip-instance
</code></pre></div>
-<div class="highlight"><pre><code>$ kubectl kudo install flink --version=0.1.1
--skip-instance
+<div class="highlight"><pre><code>$ kubectl kudo install flink --version=0.2.1
--skip-instance
</code></pre></div>
<p>This installs all the Operator versions needed for our demo.</p>
@@ -261,7 +261,7 @@ $KUDO_HOME has been configured at /Users/gerred/.kudo
<div class="highlight"><pre><code>$ cd operators
$ kubectl kudo install
repository/flink/docs/demo/financial-fraud/demo-operator --instance flink-demo
-instance.kudo.dev/v1alpha1/flink-demo created
+instance.kudo.dev/v1beta1/flink-demo created
</code></pre></div>
<p>This time we didn’t include the –skip-instance flag, so KUDO will actually
deploy all the components, including Flink, Kafka, and ZooKeeper. KUDO
orchestrates deployments and other lifecycle operations using <a
href="https://kudo.dev/docs/concepts.html#plan";>plans</a> that were defined by
the Operator developer. Plans are similar to <a
href="https://en.wikipedia.org/wiki/Runbook";>runbooks</a> and encapsulate all
the procedures required to operate the software. We can track the status [...]
@@ -269,7 +269,7 @@ instance.kudo.dev/v1alpha1/flink-demo created
<div class="highlight"><pre><code>$ kubectl kudo plan status --instance
flink-demo
Plan(s) for "flink-demo" in namespace "default":
.
-└── flink-demo (Operator-Version: "flink-demo-0.1.1" Active-Plan: "deploy")
+└── flink-demo (Operator-Version: "flink-demo-0.1.4" Active-Plan: "deploy")
└── Plan deploy (serial strategy) [IN_PROGRESS]
├── Phase dependencies [IN_PROGRESS]
│ ├── Step zookeeper (COMPLETE)
@@ -288,7 +288,7 @@ Plan(s) for "flink-demo" in namespace "default":
<div class="highlight"><pre><code>$ kubectl kudo plan status --instance
flink-demo-kafka
Plan(s) for "flink-demo-kafka" in namespace "default":
.
-└── flink-demo-kafka (Operator-Version: "kafka-0.1.3" Active-Plan: "deploy")
+└── flink-demo-kafka (Operator-Version: "kafka-1.2.0" Active-Plan: "deploy")
├── Plan deploy (serial strategy) [IN_PROGRESS]
│ └── Phase deploy-kafka [IN_PROGRESS]
│ └── Step deploy (IN_PROGRESS)
