Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

CRD on helm #228

Closed
sandromello opened this issue Jan 25, 2019 · 2 comments
Closed

CRD on helm #228

sandromello opened this issue Jan 25, 2019 · 2 comments

Comments

@sandromello
Copy link

I'm trying to add a CRD but apiextensions.k8s.io/v1beta1 it's not recognized as a valid type when building my bundle:

tele build -o bundle.tar appliance/gravity/resources/app.yaml

Ref: https://github.com/gravitational/gravity/blob/5.5.0-alpha.6/lib/app/resources/resourcefiles.go#L196

Will skip unrecognized object in Helm chart charts/kong: apiVersion=apiextensions.k8s.io/v1beta1, kind=CustomResourceDefinition
Will skip unrecognized object in Helm chart charts/kong: apiVersion=apiextensions.k8s.io/v1beta1, kind=CustomResourceDefinition
Will skip unrecognized object in Helm chart charts/kong: apiVersion=apiextensions.k8s.io/v1beta1, kind=CustomResourceDefinition
Will skip unrecognized object in Helm chart charts/kong: apiVersion=apiextensions.k8s.io/v1beta1, kind=CustomResourceDefinition

Is this intentional and there's another way of adding a CRD?

@a-palchikov
Copy link
Contributor

The warning itself is intentional and is supposed to be harmless (i.e. it should be just ignored at this point) but there's also a bug that filters the unrecognized resources.
Thanks for reporting this - we'll have this fixed.

@a-palchikov
Copy link
Contributor

Closed in #229.
And like I mentioned - the warning is there to point out that the resource has not been processed by the build operation (i.e. no docker image references were extracted).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants