[helm] Add a helm chart for Fluss #779 #1685
Conversation
dreger1997
changed the title
|
Hi, @dreger1997. If you have time. Can you rebase your branch to main? |
…svc for coordinator and headless svc for tablet
… tested with Flink inside the cluster
Done |
|
@dreger1997 Pls adding license header for your new introduce yaml files. |
There was a problem hiding this comment.
Hi, @dreger1997. Thanks for your great work. I have successfully launched Fluss in my local environment, but I feel the documentation is still insufficient. Can we provide an end-to-end guide that covers how to install it, what components are required, how to connect with Flink and create tables? Something similar to the following documentation: https://ricardo-aires.github.io/helm-charts/charts/kafka/
| apiVersion: v2 | ||
| name: fluss | ||
| description: A Helm chart for Kubernetes to deploy Apache Fluss Coordinator and Tablet servers | ||
| appVersion: "0.7.0" |
docker/helm/Chart.yaml
Outdated
|
|
||
| apiVersion: v2 | ||
| name: fluss | ||
| description: A Helm chart for Kubernetes to deploy Apache Fluss Coordinator and Tablet servers |
docker/helm/README.md
Outdated
|
|
||
| # Fluss Helm Chart | ||
|
|
||
| This chart deploys a Fluss cluster with a Coordinator and a StatefulSet of Tablets. |
| spec: | ||
| containers: | ||
| - name: {{ .Chart.Name }}-coordinator | ||
| image: "{{.Values.image.repository}}:{{ .Values.image.tag }}" |
There was a problem hiding this comment.
Do we need to add {{.Values.image.registry}}, and change this to {{.Values.image.registry}}/{{.Values.image.repository}}:{{ .Values.image.tag }}
| echo "advertised.listeners: CLIENT://coordinator-server-${FLUSS_SERVER_ID}.coordinator-server-hs.default.svc.cluster.local:{{ .Values.appConfig.externalPort }}" >> $FLUSS_HOME/conf/server.yaml && \ | ||
|
|
||
| bin/coordinator-server.sh start-foreground | ||
| # advertised.listeners: CLIENT://$(POD_NAME).fluss-tablet-hs.default.svc.cluster.local:9124 |
| echo "bind.listeners: INTERNAL://${POD_IP}:{{ .Values.appConfig.internalPort }}, CLIENT://0.0.0.0:{{ .Values.appConfig.externalPort }}" >> $FLUSS_HOME/conf/server.yaml && \ | ||
| echo "advertised.listeners: CLIENT://tablet-server-${FLUSS_SERVER_ID}.tablet-server-hs.default.svc.cluster.local:{{ .Values.appConfig.externalPort }}" >> $FLUSS_HOME/conf/server.yaml && \ | ||
| bin/tablet-server.sh start-foreground | ||
| # advertised.listeners: CLIENT://$(POD_NAME).fluss-tablet-hs.default.svc.cluster.local:9124 |
| spec: | ||
| containers: | ||
| - name: {{ .Chart.Name }}-tablet | ||
| image: "{{.Values.image.repository}}:{{ .Values.image.tag }}" |
There was a problem hiding this comment.
Ditto. Do we need to add {{.Values.image.registry}}, and change this to {{.Values.image.registry}}/{{.Values.image.repository}}:{{ .Values.image.tag }}
There was a problem hiding this comment.
see my comment below to the registry
|
|
||
| image: | ||
| repository: fluss/fluss | ||
| tag: "0.7.0" |
There was a problem hiding this comment.
https://hub.docker.com/r/fluss/fluss the latest Fluss image is 0.7
| # This is a YAML-formatted file. | ||
| # Declare variables to be passed into your templates. | ||
|
|
||
| image: |
There was a problem hiding this comment.
Do we need to add image:registry?
There was a problem hiding this comment.
I think we do not need it as it takes it from the Docker Hub
| --set replicaCount=3 \ | ||
| --set auth.enabled=false \ | ||
| --set persistence.size=5Gi | ||
|
|
There was a problem hiding this comment.
We need to add more contents in Readme to introduce how to build a fluss cluster and operate by fluss in helm charts
Purpose
Linked issue: close #779
Creating a V1 Draft for Helm-charts with Apache Fluss and external Zookeeper
Brief change log
Tests
API and Format
Documentation
This is currently not working with CLIENTS external to the K8s Cluster