You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/getting_started.adoc
+22-19Lines changed: 22 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,30 +74,32 @@ CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/servi
74
74
Metrics-server is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
75
75
----
76
76
77
-
=== Installing Helm
78
-
Stackable uses https://helm.sh/[Helm] as the package manager for its Kubernetes operators. This greatly simplifies the deployment and management of Kubernetes operators and CRDs. The quickest way to install Helm is to run the following command:
77
+
== Installing Stackable
78
+
=== Install stackablectl
79
+
80
+
Install the Stackable command line utility xref:stackablectl::index.adoc[stackablectl] by following the installation steps for your platform on the xref:stackablectl::installation.adoc[installation] page.
81
+
82
+
=== Installing Stackable Operators
83
+
The Stackable operators are components that translate the service definitions deployed via Kubernetes into deploy services on the worker nodes. These can be installed on any node that has access to the Kubernetes control plane. In this example we will install them on the controller node.
84
+
85
+
Stackable operators are installed using stackablectl. Run the following commands to install the latest operator versions of ZooKeeper, Kafka and NiFi.
With Helm installed you can add the Stackable operator repo, where the helm charts to install Stackable operators can be found. There are development, test and a stable repositories available, we'll be using the stable repo in this guide.
The Stackable operators are components that translate the service definitions deployed via Kubernetes into deploy services on the worker nodes. These can be installed on any node that has access to the Kubernetes control plane. In this example we will install them on the controller node.
97
-
98
-
Stackable operators are installed using Helm charts. Run the following commands to install the operators for ZooKeeper, Kafka and NiFi using the repo configured earlier. The --devel flag will choose the latest available version; alternatively the --version flag can be used to deploy a specific version.
99
-
100
-
==== Install operators from the Stackable repository
Copy file name to clipboardExpand all lines: modules/tutorials/pages/end-to-end_data_pipeline_example.adoc
+69-7Lines changed: 69 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,22 @@ You should make sure that you have everything you need:
13
13
14
14
* A running Kubernetes cluster
15
15
* https://kubernetes.io/docs/tasks/tools/#kubectl[Kubectl] to interact with the cluster
16
-
* https://helm.sh/[Helm] to deploy Operators and some dependencies
17
-
* Shell utilities like `cat` and `curl`
18
-
19
-
Throughout the tutorial you will install Operators from the Stackable Helm repository using Helm. To easily install from the Stackable repository, add a link to it to your Helm repository list:
16
+
* https://helm.sh/[Helm] to deploy third-party dependencies
17
+
* xref:stackablectl::installation.adoc[stackablectl] to install and interact with Stackable operators
18
+
+
19
+
[NOTE]
20
+
====
21
+
While we recommend to use stackablectl, you can also install operators from the Helm Chart repository:
Apache NiFi and Apache Kafka both use Apache ZooKeeper as backing config storage, so the xref:zookeeper::index.adoc[Stackable Operator for Apache ZooKeeper] has to be installed in order to make sure that a ZooKeeper cluster can be rolled out.
44
62
There is no need to install multiple ZooKeeper clusters, as NiFi, Kafka and Druid can share the same cluster via provisioning a ZNode per backed service.
0 commit comments