Skip to content

[helm] Add existingSecret support for SASL credentials #3172

@fresh-borzoni

Description

@fresh-borzoni

Search before asking

  • I searched in the issues and found nothing similar.

Description

The Fluss Helm chart currently renders SASL credentials directly from values.yaml into a Helm-managed Secret. This forces operators to either commit plaintext passwords to values.yaml (and the Helm release storage) or fork the chart to integrate with external secret sources like External Secrets Operator.

The chart should allow each listener to reference a pre-existing Kubernetes Secret for its credentials, keeping plaintext passwords out of the Helm release and out of values.yaml.

Willingness to contribute

  • I'm willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions