swuferhong commented on code in PR #1685:
URL: https://github.com/apache/fluss/pull/1685#discussion_r2415760834


##########
docker/helm/README.md:
##########
@@ -0,0 +1,72 @@
+
+# Fluss Helm Chart
+
+This chart deploys an Apache Fluss cluster on Kubernetes, following Helm best 
practices.
+It requires a Zookeeper ensemble to be running in the same Kubernetes cluster. 
In future releases, we may add support for an embedded Zookeeper cluster.
+
+
+## Requirements 
+
+| component                                                                    
  | version |
+| 
------------------------------------------------------------------------------ 
| ------- |
+| [Docker](https://docs.docker.com/)                                           
  | v28.3.2 |
+| [Minikube](https://minikube.sigs.k8s.io/docs/)                               
  | v1.36.0 |
+| [Kubernetes](https://kubernetes.io)                                          
  | v1.25.3 |
+| [Helm](https://helm.sh)                                                      
  | v3.18.6 |
+| [Apache Fluss](https://fluss.apache.org/docs/)                               
  | v0.7.0  |
+
+A container image for Fluss is available on DockerHub as `fluss/fluss:0.7.0`. 
You can use it directly or build your own from this repo.
+
+## Overview
+
+It creates:
+- 1x CoordinatorServer as a StatefulSet with a headless Service (stable 
per‑pod DNS)
+- 3x TabletServers as a StatefulSet with a headless Service (stable per‑pod 
DNS)
+- ConfigMap for server.yaml (CoordinatorServer and TabletServers) to override 
default Fluss configuration
+- Optional PersistentVolumes for data directories
+
+## Quick start
+
+1) Default (Zookeeper available in-cluster):
+
+```bash
+helm install fluss ./fluss-helm
+```
+
+2) ZooKeeper deployment:
+
+To start Zookeeper use Bitnami’s chart or your own deployment. Example with 
Bitnami’s chart:
+
+```bash
+helm repo add bitnami https://charts.bitnami.com/bitnami
+helm repo update
+helm install zk bitnami/zookeeper \
+  --set replicaCount=3 \
+  --set auth.enabled=false \
+  --set persistence.size=5Gi
+```

Review Comment:
   `helm install zk` first? Otherwise, Fluss cannot normal startup.



##########
docker/helm/README.md:
##########
@@ -0,0 +1,72 @@
+
+# Fluss Helm Chart
+
+This chart deploys an Apache Fluss cluster on Kubernetes, following Helm best 
practices.
+It requires a Zookeeper ensemble to be running in the same Kubernetes cluster. 
In future releases, we may add support for an embedded Zookeeper cluster.
+
+
+## Requirements 
+
+| component                                                                    
  | version |
+| 
------------------------------------------------------------------------------ 
| ------- |
+| [Docker](https://docs.docker.com/)                                           
  | v28.3.2 |
+| [Minikube](https://minikube.sigs.k8s.io/docs/)                               
  | v1.36.0 |
+| [Kubernetes](https://kubernetes.io)                                          
  | v1.25.3 |
+| [Helm](https://helm.sh)                                                      
  | v3.18.6 |
+| [Apache Fluss](https://fluss.apache.org/docs/)                               
  | v0.7.0  |
+
+A container image for Fluss is available on DockerHub as `fluss/fluss:0.7.0`. 
You can use it directly or build your own from this repo.
+
+## Overview
+
+It creates:
+- 1x CoordinatorServer as a StatefulSet with a headless Service (stable 
per‑pod DNS)
+- 3x TabletServers as a StatefulSet with a headless Service (stable per‑pod 
DNS)
+- ConfigMap for server.yaml (CoordinatorServer and TabletServers) to override 
default Fluss configuration
+- Optional PersistentVolumes for data directories
+
+## Quick start
+
+1) Default (Zookeeper available in-cluster):
+
+```bash
+helm install fluss ./fluss-helm
+```

Review Comment:
   Do we need to specify the namespace? If not, the Zookeeper address may need 
to be modified.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to