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

[rbac-manager] Unable to install with Helm 3 #276

Closed
bittermandel opened this issue Apr 14, 2020 · 3 comments
Closed

[rbac-manager] Unable to install with Helm 3 #276

bittermandel opened this issue Apr 14, 2020 · 3 comments
Assignees

Comments

@bittermandel
Copy link

Describe the bug
When installing fairwinds-stable/rbac-manager using helm3, validation fails with the following error:
Error: validation: chart.metadata is required

To Reproduce
Steps to reproduce the behavior:

  1. helm install fairwinds-stable/rbac-manager rbac-manager --namespace rbac-manager

Expected behavior
Should install the chart as intended.

CLI Output
Error: validation: chart.metadata is required

Environment (please complete the following information):

  • Helm Version: 3.1.2
  • Kubernetes Version 1.18.0

Additional context
I can't find much information about Helm 3 support in this repository, but I can see that you test for helm 3 support. Am I missing something?

@lucasreed
Copy link
Contributor

Thanks for bringing this to our attention. It certainly looks related to this issue in helm. Since our tests are installing with a local copy of the chart it makes sense that tests are passing. We will investigate what changes we can potentially make to ensure it works in both helm 2 and 3.

@lucasreed lucasreed self-assigned this Apr 14, 2020
@bittermandel
Copy link
Author

bittermandel commented Apr 14, 2020

Sorry, this was just a misleading error message by Helm. I used the wrong order of chart name and release name! Took a while to figure out 😄

PS: We good. Issue can be closed!

@lucasreed
Copy link
Contributor

Ah ok, good to know. Glad it's working and thanks for the update!

This issue was closed.
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

No branches or pull requests

2 participants