oneuptime-secrets resource registers in default namespace instead of helm chart namespace #516

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

Originally created by @cpellet on 4/3/2025

Describe the bug
When deploying the helm chart with minimal required configuration, the essential "oneuptime-secrets" secret is deployed on the "default"namespace, with no option to specify a different one via a resource template:

kind: Secret
metadata:
  name: {{
printf
"%s-%s" $.Release.Name "secrets" }}
  annotations:
    "helm.sh/resource-policy": "keep"

To Reproduce
Steps to reproduce the behavior:

  1. Deploy helm chart on a non-default namespace

Expected behavior
All pods start and reach ready state successfully

Actual behaviour
Many pods fail due to a config error, as the oneuptime-secrets resource isn't resolved

*Originally created by @cpellet on 4/3/2025* **Describe the bug** When deploying the helm chart with minimal required configuration, the essential "oneuptime-secrets" secret is deployed on the "default"namespace, with no option to specify a different one via a resource template: ```apiVersion: v1 kind: Secret metadata: name: {{ printf "%s-%s" $.Release.Name "secrets" }} annotations: "helm.sh/resource-policy": "keep" ``` **To Reproduce** Steps to reproduce the behavior: 1. Deploy helm chart on a non-default namespace **Expected behavior** All pods start and reach ready state successfully **Actual behaviour** Many pods fail due to a config error, as the oneuptime-secrets resource isn't resolved
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#516