Skip to content

Commit 0c1700a

Browse files
committed
Include deploy instructions
There are now github releases so the Helm chart can be referred to using an URI.
1 parent d9336ea commit 0c1700a

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

README.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,25 @@ Finally, it is possible to ingest logs from a file on the container filesystem.
1414

1515
## Try it out
1616

17-
The easiest way to get started is using the helm chart. As it is not published you need to check out the code:
17+
The easiest way to get started is using the Helm chart. Official images are not published yet, so you need to pass the image.repository and image.tag manually:
1818

1919
```bash
2020
git clone [email protected]:vmware/kube-fluentd-operator.git
21-
helm install --name kfo ./kube-fluentd-operator/log-router --set rbac.create=true
21+
helm install --name kfo ./kube-fluentd-operator/log-router \
22+
--set rbac.create=true \
23+
--set image.tag=v1.1.0-beta-1 \
24+
--set image.repository=jvassev/kube-fluentd-operator
25+
```
26+
27+
Alternatively, deploy the Helm chart from a Github release:
28+
29+
```bash
30+
CHART_URL='https://github.com/vmware/kube-fluentd-operator/releases/download/v1.1.0-beta-1/log-router-0.2.0.tgz'
31+
32+
helm install --name kfo ${CHART_URL} \
33+
--set rbac.create=true \
34+
--set image.tag=v1.1.0-beta-1 \
35+
--set image.repository=jvassev/kube-fluentd-operator
2236
```
2337

2438
Then create a namespace `demo` and a configmap describing where all logs from `demo` should go to. The configmap must contain an entry called "fluent.conf". Finally, point the kube-fluentd-operator to this configmap using annotations.

0 commit comments

Comments
 (0)