Update Blog “deploying-cribl-stream-containers-on-hpe-greenlake”

Author: ealagna

content/blog/deploying-cribl-stream-containers-on-hpe-greenlake.md

@@ -25,7 +25,7 @@ Deploying Cribl Stream containers on HPE GreenLake offers a number of advantages
 
 ![Cribl architecture diagram](/img/criblarchitecure.png "Cribl architecture")
 
-## Prerequisites
+#### Prerequisites
 
 Before you deploy Cribl Stream containers on HPE GreenLake, you will need to:
 
@@ -81,22 +81,22 @@ The Cribl Stream helm charts can be found on github (<https://github.com/criblio
 
 Log into cloud CLI or jump box and issue the following commands:
 
-```yaml
+```shell
 export KUBECONFIG=<path_to_kube_settings>
 kubectl get nodes -n cribl
 kubectl get svc  -n cribl
 ```
 
 Label the leader node and the worker nodes:
 
-```yaml
+```shell
 kubectl label nodes <leader_node> stream=leader
 kubectl label nodes <worker_node> stream=worker
 ```
 
 Validate by running:
 
-```yaml
+```shell
 kubectl get nodes --show-labels
 ```
 
@@ -112,4 +112,113 @@ For the worker nodes, create a file named `Worker_values.yaml` and modify line 9
 ```yaml
 nodeSelector:
      stream: worker
-```
+```
+
+Next set the labels for your workers and leader node.
+
+First get a list of all the nodes and see the labels associated with them:
+
+```shell
+kubectl get nodes --show-labels
+```
+
+Now, identify the nodes and make sure to label the nodes according to their role for this deployment. 
+
+Here is an example of setting the host `k8s-cribl-master-t497j-92m66.gl-hpe.net` as a leader:
+
+```shell
+kubectl label nodes k8s-cribl-master-t497j-92m66.gl-hpe.net stream=leader
+```
+
+Here is an example of setting the host `k8s-cribl-wor8v32g-cdjdc-8tkhn.gl-hpe.net` as a worker node:
+
+```shell
+kubectl label nodes k8s-cribl-wor8v32g-cdjdc-8tkhn.gl-hpe.net stream=worker
+```
+
+If you accidentally label a node and want to remove or overwrite the label, you can use this command:
+
+```shell
+kubectl label nodes k8s-cribl-wor8v32g-cdjdc-876nq.gl-hpe.net stream=worker --overwrite=true
+```
+
+Once the labels have been set, now you are ready to run the helm command and deploy Cribl Stream on your environment. The first command will deploy the Cribl Leader node:
+
+```shell
+helm install --generate-name cribl/logstream-leader -f leader_values.yaml -n cribl
+```
+
+When successful, you will see a similar output like the one below: 
+
+```shell
+NAME: logstream-leader-1696441333
+LAST DEPLOYED: Wed Oct  4 17:42:16 2023
+NAMESPACE: default
+STATUS: deployed
+REVISION: 1
+TEST SUITE: None
+```
+
+Note that this will deploy the leader node with the parameters found in the `leader_values.yaml` file and into the namespace `cribl`. 
+
+Next, deploy the worker nodes using the `worker_values.yaml` file into the namespace `cribl`.
+
+```shell
+helm install --generate-name cribl/logstream-workergroup -f workers_values.yaml
+```
+
+When successful, you will see a similar output like the one below:
+
+```shell
+NAME: logstream-workergroup-1696441592
+LAST DEPLOYED: Wed Oct  4 17:46:36 2023
+NAMESPACE: default
+STATUS: deployed
+REVISION: 1
+TEST SUITE: None
+```
+
+Now you can validate the deployment by running the following command:
+
+```shell
+kubectl get svc
+```
+
+You should see the following results:
+
+```shell
+NAME    	                          TYPE       	 CLUSTER-IP   	 EXTERNAL-IP  PORT(S)                                                                                                                                                    AGE
+kubernetes                         	  ClusterIP  	 10.96.0.1    	 <none>    	  443/TCP                                                                                                                                                  	 22d
+logstream-leader-1696441333        	  LoadBalancer   10.111.152.178  <pending> 	  9000:31200/TCP                                                                                                                                           	 9m56s
+logstream-leader-1696441333-internal  ClusterIP      10.105.14.164	 <none>    	  9000/TCP,4200/TCP                                                                                                                                        	 9m56s
+logstream-workergroup-1696441592   	  LoadBalancer   10.102.239.137  <pending> 	  10001:30942/TCP,9997:32609/TCP,10080:32174/TCP,10081:31898/TCP,5140:30771/TCP,8125:31937/TCP,9200:32134/TCP,8088:32016/TCP,10200:32528/TCP,10300:30836/TCP 5m35s
+```
+
+Note, the names and IP addresses will differ from the above example. To test that the deployment was successful, you can run the following command and log into your deployment using the localhost and port 9000:
+
+```shell
+kubectl port-forward service/logstream-leader-1696441333 9000:9000 &
+```
+
+#### Uninstalling Cribl using Helm
+
+You can uninstall the Cribl deployment for both the leader and worker nodes by running the following commands respectively:
+
+```shell
+helm uninstall logstream-leader-1696441333 -n default
+helm uninstall logstream-workergroup-1696441592 -n default
+```
+
+Make sure to use your leader and worker group name when uninstalling Cribl from your deployment.
+
+#### Configuring Cribl Stream
+
+Once you have deployed the Cribl Stream containers, you need to configure them to collect and process your data. You can do this by editing the Cribl Stream configuration file. The Cribl Stream documentation provides detailed instructions on how to configure Cribl Stream.
+
+#### Sending your data to your analysis platform of choice
+
+Once you have configured Cribl Stream to collect and process your data, you need to send it to your analysis platform of choice. Cribl Stream supports a wide range of analysis platforms, including Elasticsearch, Splunk, and Kafka.
+
+#### Conclusion
+
+Deploying Cribl Stream containers on HPE GreenLake is a simple and effective way to implement a vendor-agnostic observability pipeline. Cribl Stream containers offer a number of advantages, including agility, cost savings, security, and management simplicity.