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

error validating "kafka/kustomization.yaml #269

Closed
spanningwings opened this issue May 2, 2019 · 5 comments
Closed

error validating "kafka/kustomization.yaml #269

spanningwings opened this issue May 2, 2019 · 5 comments

Comments

@spanningwings
Copy link

Hi,

When I did 'kubectl apply -f ./kafka', I got "error: error validating "kafka/kustomization.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false"

Is this file useful?

Thanks,

@mithunmx
Copy link

mithunmx commented May 3, 2019

Facing the same issue. Can anyone help us on the same ? Running on kubectl in GKE

@solsson
Copy link
Contributor

solsson commented May 3, 2019

Is this file useful?

Yes! I'm only just learning Kustomize (kubectl apply -k) but it already appears highly useful. I'll add some new PRs to really overuse it :) and then we can assess.

I found no other option than to place kustomization.yaml in each folder. One at the top level would defeat composability (see https://github.com/Yolean/kubernetes-kafka/tree/storagclass-kustomize/variants) and Kustomize won't allow resources from a parent folder.

I'd like it if kubernetes-kafka is still applyable as-is, without error messages. Any ideas towards that are welcome.

@mithunmx
Copy link

mithunmx commented May 3, 2019

@solsson do you have any suggestion on how to fix the error / any workaround for the issue error: error validating "kafka/kustomization.yaml": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false"

@solsson
Copy link
Contributor

solsson commented May 3, 2019

I think that upgrading to kubectl 1.14+ and applying a dummy kustomization is a decent workaround, but I have no real fix. As I wrote above I hope someone can point us towards an alternative.

@solsson
Copy link
Contributor

solsson commented May 9, 2019

I had a flash of insight :)

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

3 participants