Skip to content

Conversation

@namm2
Copy link

@namm2 namm2 commented Dec 29, 2025

Use secretKeyRef to not expose Clickhouse credentials into runtime environment

Signed-off-by: Nam Hai Nguyen <[email protected]>
@CLAassistant
Copy link

CLAassistant commented Dec 29, 2025

CLA assistant check
All committers have signed the CLA.

Signed-off-by: Nam Hai Nguyen <[email protected]>
@HamseTelia
Copy link

Could we also please add the clickhouse user's password to be referenced from a secret clickhouse.config.users.appUserPassword. Like suggested here: #125

clickhouse:
  config:
    users:
      # Existing inline password support (for backward compatibility)
      appUserPassword: "hyperdx"
      otelUserPassword: "otelcollectorpass"
      otelUserName: "otelcollector"
      
      # NEW: External secret support
      useExternalSecret: false
      externalSecret:
        name: ""
        appUserPasswordKey: "app-user-password"

@namm2
Copy link
Author

namm2 commented Jan 14, 2026

Could we also please add the clickhouse user's password to be referenced from a secret clickhouse.config.users.appUserPassword. Like suggested here: #125

I think this is a different use case

Copy link
Collaborator

@dhable dhable left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution. There's a merge conflict, probably around the version, that needs to be resolved. If you revert the Chart.yaml change, it should allow merging in main into your PR branch.

We also would like a changeset in the PR as well. You can create this by running yarn install from the root to install the changeset CLI. Then run yarn changeset and follow the prompts to generate the required files. We can't generate a release without that.

url: https://github.com/hyperdxio/hyperdx
type: application
version: 1.0.1
version: 1.0.2
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will be incremented by our release action when we decide to cut a new release. Please revert this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants