Skip to content

Commit df7c8b0

Browse files
committed
Update Blog “deploying-cribl-stream-containers-on-hpe-greenlake”
1 parent ec000f5 commit df7c8b0

File tree

1 file changed

+90
-3
lines changed

1 file changed

+90
-3
lines changed

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

Lines changed: 90 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,8 @@ tags:
1212
---
1313
Hewlett Packard Enterprise and [Cribl](https://cribl.io/) bring together breakthrough technology to optimize and modernize observability data management offering new levels of performance and platform independence.
1414

15-
1615
The challenges of security and log management are only partly solved by existing software solutions. HPE and Cribl address the remaining problems of optimizing, routing, and replaying logs to provide independence from the industry’s software products in this space. HPE provides a robust way to run multiple log management software solutions and the Cribl Stream in a modern, easy-to-use, and robust platform. Together HPE and Cribl reduce the total cost of ownership of log management systems by optimizing the software, accelerating infrastructure, and reducing management costs.
1716

18-
1917
Cribl Stream is a vendor-agnostic observability pipeline that gives you the flexibility to collect, reduce, enrich, normalize, and route data from any source to any destination within your existing data infrastructure. HPE GreenLake is a private and hybrid cloud service that delivers the benefits of public cloud to your on-premises environment.
2018

2119
Deploying Cribl Stream containers on HPE GreenLake offers a number of advantages, including:
@@ -25,4 +23,93 @@ Deploying Cribl Stream containers on HPE GreenLake offers a number of advantages
2523
* **Security:** Cribl Stream containers can help you secure your data by encrypting it at rest and in transit.
2624
* **Management simplicity:** HPE GreenLake provides a single management console for managing your Cribl Stream containers, making it easy to keep your observability pipeline running smoothly.
2725

28-
![Cribl architecture diagram](/img/criblarchitecure.png "Cribl architecture")
26+
![Cribl architecture diagram](/img/criblarchitecure.png "Cribl architecture")
27+
28+
## Prerequisites
29+
30+
Before you deploy Cribl Stream containers on HPE GreenLake, you will need to:
31+
32+
* Have a HPE GreenLake account on <https://common.cloud.hpe.com/>.
33+
* Install the HPE GreenLake CLI.
34+
* Create a HPE GreenLake cluster.
35+
* Install the Cribl Stream Kubernetes operator.
36+
37+
Steps to deploy Cribl Stream containers on HPE GreenLake:
38+
39+
1. Create a Cribl Stream deployment file. This file will specify the Cribl Stream containers that you want to deploy, as well as the resources that they need.
40+
2. Deploy the Cribl Stream containers to your HPE GreenLake cluster using the Cribl Stream Kubernetes operator.
41+
3. Verify that the Cribl Stream containers are running and healthy.
42+
4. Configure Cribl Stream to collect and process your data.
43+
5. Send your data to your analysis platform of choice.
44+
45+
#### Example deployment file
46+
47+
The following example deployment file deploys a Cribl Stream container that collects and processes logs from a Kubernetes cluster:
48+
49+
```yaml
50+
apiVersion: apps/v1
51+
kind: Deployment
52+
metadata:
53+
name: cribl-stream
54+
spec:
55+
replicas: 1
56+
selector:
57+
matchLabels:
58+
app: cribl-stream
59+
template:
60+
metadata:
61+
labels:
62+
app: cribl-stream
63+
spec:
64+
containers:
65+
- name: cribl-stream
66+
image: cribl/cribl-stream:latest
67+
ports:
68+
- containerPort: 9000
69+
volumeMounts:
70+
- name: cribl-stream-config
71+
mountPath: /etc/cribl-stream
72+
volumes:
73+
- name: cribl-stream-config
74+
configMap:
75+
name: cribl-stream-config
76+
```
77+
78+
#### Deploying Cribl Stream using Helm Charts
79+
80+
The Cribl Stream helm charts can be found on github (<https://github.com/criblio/helm-charts>). This assumes that the namespace is set to `cribl`.
81+
82+
Log into cloud CLI or jump box and issue the following commands:
83+
84+
```yaml
85+
export KUBECONFIG=<path_to_kube_settings>
86+
kubectl get nodes -n cribl
87+
kubectl get svc -n cribl
88+
```
89+
90+
Label the leader node and the worker nodes:
91+
92+
```yaml
93+
kubectl label nodes <leader_node> stream=leader
94+
kubectl label nodes <worker_node> stream=worker
95+
```
96+
97+
Validate by running:
98+
99+
```yaml
100+
kubectl get nodes --show-labels
101+
```
102+
103+
Create and modify the `values.yaml` file for workers and leader nodes. For the leader nodes, create a file named `Leader_values.yaml` and modify line 97:
104+
105+
```yaml
106+
nodeSelector:
107+
stream: leader
108+
```
109+
110+
For the worker nodes, create a file named `Worker_values.yaml` and modify line 97:
111+
112+
```yaml
113+
nodeSelector:
114+
stream: worker
115+
```

0 commit comments

Comments
 (0)