Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in Helm Chart in file role-binding.yaml #1493

Closed
as-rail opened this issue Mar 20, 2024 · 0 comments · Fixed by #1494
Closed

Bug in Helm Chart in file role-binding.yaml #1493

as-rail opened this issue Mar 20, 2024 · 0 comments · Fixed by #1494

Comments

@as-rail
Copy link

as-rail commented Mar 20, 2024

Which component:
The name (and version) of the affected component (controller or kubeseal)

controller helm chart, version 2.15.1

Describe the bug
A clear and concise description of what the bug is.

Helm Chart cannot be rendered with additional namespaces set.
The problem is here: helm/sealed-secrets/templates/role-binding.yaml on Line 66.

There is a missing $. The line should be:

{{- if $.Values.commonAnnotations }}

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Run the command '....'
  3. Wait for '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Version of Kubernetes:

  • Output of kubectl version:
(paste your output here)

Additional context
Add any other context about the problem here.

@as-rail as-rail added the triage Issues/PRs that need to be reviewed label Mar 20, 2024
@agarcia-oss agarcia-oss added bug good first issue and removed triage Issues/PRs that need to be reviewed labels Mar 21, 2024
alemorcuq added a commit that referenced this issue Mar 21, 2024
**Description of the change**
Use the right context for `commonAnnotations` in namespaced role
bindings.

**Benefits**
Fix a bug preventing namespaced role bindings to be created.

**Applicable issues**
- fixes #1493

Signed-off-by: Alejandro Moreno <amorenoc@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants