-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Helm3 lint fails when using Kind: List #8615
Comments
Kubernetes objects should have a metadata section with a name property. Helm v2 did not check that names were present or valid, during lint. Helm v3 does. That is why you see that now. List is not a resource but rather a list of resources. There is an explanation at kubernetes/kubectl#837 (comment). No official documentation exists on it. I have not tried to send a list to Kubernetes. If it works we should handle linting that case. |
Yes Kind:List works on Kubernetes , and if i do upgrade or install with Helm3.3 it works, its just that the lint fails on linux only. |
That being the case on Windows is surprising. We'll need to look into it. Thanks for that piece of detail. |
/assign |
Hello, since Helm 3.3.0 I have problems with liniting the following resource:
With Helm 3.2.4 it worked. Is this related to this issue or should I open a separate one? EDIT: With Helm 3.2.4 I could also lint the above mentioned resource:
And with Helm 3.3.0 I also get this error:
|
@dbluxo this is related. All lists are affected. This is due to a new linting feature in Helm 3.3.0. |
Helm v2 didn't validate that resource names were valid. Helm v3 introduces this check, failing lint checks that were previously passing. This PR adds a check to validate metadata for a list of resources if present, otherwise falling back to previous behavior of validating the metadata. Fixes helm#8615
Helm v2 didn't validate that resource names were valid. Helm v3 introduces this check, failing lint checks that were previously passing. This PR adds a check to validate metadata for a list of resources if present, otherwise falling back to previous behavior of validating the metadata. Fixes helm#8615 Signed-off-by: Chris Bui <christopher.d.bui@gmail.com>
Helm v2 didn't validate that resource names were valid. Helm v3 introduces this check, failing lint checks that were previously passing. This PR adds a check to validate metadata for a list of resources if present, otherwise falling back to previous behavior of validating the metadata. Fixes helm#8615 Signed-off-by: Chris Bui <christopher.d.bui@gmail.com>
Helm v2 didn't validate that resource names were valid. Helm v3 introduces this check, failing lint checks that were previously passing. This PR adds a check to validate metadata for a list of resources if present, otherwise falling back to previous behavior of validating the metadata. Fixes helm#8615 Signed-off-by: Chris Bui <christopher.d.bui@gmail.com>
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
The workaround for this is probably to configure the list with a
|
This workaround is not always valid, please see kubernetes-sigs/kustomize#688 |
How is this related? |
It still fails with |
Issues during lint with resource Kind:List - object name does not conform to Kubernetes naming requirements
Using Helm 3.3 on linux
helm lint --strict <>
======
Helm 2 does not fail with same resource.
The text was updated successfully, but these errors were encountered: