Support existing secrets for Redis & ClickHouse #135

Closed
opened 2026-04-05 16:18:56 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @matiaschileno on 1/27/2026

Description

Allows referencing existing Kubernetes secrets for ClickHouse and Redis passwords (compatible with already in-place auto-generated passwords).

Usage

ClickHouse:

clickhouse:
  auth:
    existingSecret:
      name: my-clickhouse-secret
      passwordKey: admin-password

Redis:

redis:
  auth:
    existingSecret:
      name: my-redis-secret
      passwordKey: password

Pull Request Checklist:

  • Please make sure all jobs pass before requesting a review.
  • Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
  • Have you lint your code locally before submission?
  • Did you write tests where appropriate?
*Originally created by @matiaschileno on 1/27/2026* ### Description Allows referencing existing Kubernetes secrets for ClickHouse and Redis passwords (compatible with already in-place auto-generated passwords). ## Usage **ClickHouse:** ```yaml clickhouse: auth: existingSecret: name: my-clickhouse-secret passwordKey: admin-password ``` **Redis:** ```yaml redis: auth: existingSecret: name: my-redis-secret passwordKey: password ``` ### Pull Request Checklist: - [ ] Please make sure all jobs pass before requesting a review. - [ ] Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). - [ ] Have you lint your code locally before submission? - [ ] Did you write tests where appropriate?
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#135