@@ -36,7 +36,7 @@ the installation documentation provides instructions for deploying one using Bit
3636
3737### Running Fluss locally with Minikube
3838
39- For local testing and development, you can deploy Fluss on Minikube. This is ideal for development, testing, and learning purposes.
39+ For local testing and development, you can deploy Fluss on Minikube. This is ideal for development, testing and learning purposes.
4040
4141#### Prerequisites
4242
@@ -157,7 +157,7 @@ kubectl logs -l app.kubernetes.io/component=tablet
157157
158158## Configuration Parameters
159159
160- The following table lists the configurable parameters of the Fluss chart and their default values.
160+ The following table lists the configurable parameters of the Fluss chart, and their default values.
161161
162162### Global Parameters
163163
@@ -225,6 +225,13 @@ The following table lists the configurable parameters of the Fluss chart and the
225225| ` resources.tabletServer.limits.cpu ` | CPU limits for tablet servers | Not set |
226226| ` resources.tabletServer.limits.memory ` | Memory limits for tablet servers | Not set |
227227
228+ ### SASL Parameters
229+
230+ | Parameter | Description | Default |
231+ | -----------| -------------| ---------|
232+ | ` sasl.mechanism ` | SASL mechanism | ` PLAIN ` |
233+ | ` sasl.users ` | User list for PLAIN authentication | ` [{username: admin, password: password}] ` |
234+ | ` sasl.existingSecret ` | Use existing secret containing ` jaas.conf ` | ` "" ` |
228235
229236## Advanced Configuration
230237
@@ -245,16 +252,47 @@ The chart automatically configures listeners for internal cluster communication
245252- **Internal Port (9123)**: Used for internal communication within the cluster
246253- **Client Port (9124)**: Used for client connections
247254
248- Custom listener configuration:
255+ Default listeners configuration:
249256
250257` ` ` yaml
251258listeners :
252259 internal :
260+ protocol : PLAINTEXT
253261 port : 9123
254262 client :
263+ protocol : PLAINTEXT
255264 port : 9124
256265` ` `
257266
267+ To enable SASL based authentication, set any of the protocols to ` SASL`.
268+
269+ # ## Enabling Secure Connection
270+
271+ With the helm deployment, you can specify authentication protocols when connecting to the Fluss cluster.
272+
273+ The following table shows the supported protocols and security they provide :
274+
275+ | Method | Authentication | TLS Encryption |
276+ |-------------|:--------------:|:------------------:|
277+ | `PLAINTEXT` | No | No |
278+ | `SASL` | Yes | No |
279+
280+ By default, the `PLAINTEXT` protocol is used.
281+
282+ The SASL authentication will be enabled if any of the listener protocols is using `SASL`.
283+
284+ Set these values for additional configurations :
285+
286+ ` ` ` yaml
287+ sasl:
288+ mechanism: PLAIN
289+ users:
290+ - username: admin
291+ password: password
292+ ` ` `
293+
294+ The `users` defines comma-separated list of usernames and passwords for client communications when SASL is enabled.
295+
258296# ## Storage Configuration
259297
260298Configure different storage volumes for coordinator or tablet pods :
0 commit comments