Fix externalClickhouse password secret #664

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

Originally created by @fzamperin on 9/29/2024

Title of this pull request?

Fix Helm Chart Deployment Fails when using External Clickhouse

Small Description?

According to the issue, when using external clickhouse, for some reason the base64 was invalid avoiding installing/upgrading the helm chart causing: Error from server (BadRequest): error when creating "secret.yaml": Secret in version "v1" cannot be handled as a Secret: illegal base64 data at input byte 8. Unfortunately I didn't find the root cause of the problem, even when debugging it was giving the right value for the k8s secret, so I decided to instead of encode the value to base64 and use data I changed it to stringData which lets k8s encode the values.

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?

closes #1713

Screenshots (if appropriate):

https://github.com/user-attachments/assets/9f4324f7-81a7-42d4-a957-3ac25ae8d696

*Originally created by @fzamperin on 9/29/2024* ### Title of this pull request? Fix Helm Chart Deployment Fails when using External Clickhouse ### Small Description? According to the issue, when using external clickhouse, for some reason the base64 was invalid avoiding installing/upgrading the helm chart causing: `Error from server (BadRequest): error when creating "secret.yaml": Secret in version "v1" cannot be handled as a Secret: illegal base64 data at input byte 8`. Unfortunately I didn't find the root cause of the problem, even when debugging it was giving the right value for the k8s secret, so I decided to instead of encode the value to base64 and use `data` I changed it to `stringData` which lets k8s encode the values. ### 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? ### Related Issue? closes #1713 ### Screenshots (if appropriate): https://github.com/user-attachments/assets/9f4324f7-81a7-42d4-a957-3ac25ae8d696
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#664