-
Notifications
You must be signed in to change notification settings - Fork 397
[helm] Add a helm chart for Fluss #779 #1685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0.8-SNAPSHOT
|
||
image: | ||
repository: fluss/fluss | ||
tag: "0.7.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0.8-SNAPSHOT
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://hub.docker.com/r/fluss/fluss the latest Fluss image is 0.7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, @dreger1997. Even though it is not possible to download 0.8-SNAPSHOT
from remote repo, according to development standards, it's still required to use 0.8-SNAPSHOT
. During the release, this will be changed to 0.8.0
. Other projects are also managed in the same way. If users need to use the 0.8-SNAPSHOT
image, they need build it locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dreger1997. Here are some minor suggestions.
--set replicaCount=3 \ | ||
--set auth.enabled=false \ | ||
--set persistence.size=5Gi | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
helm install zk
first? Otherwise, Fluss cannot normal startup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but in the case zk is already installed then we do not need it. But I'll make it more clear
|
||
```bash | ||
helm install fluss ./fluss-helm | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to specify the namespace? If not, the Zookeeper address may need to be modified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Namespace is default, you are right needs to be added in the docs that value should be modified
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