Deploying helm charts with CRDs fails with Error: unable to build kubernetes objects from release manifest: unable to recognize ""...

[Martin-Weiss]

Tried to deploy i.e. https://github.com/zalando/postgres-operator as helm chart and this fails with

Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "OperatorConfiguration" in version "acid.zalan.do/v1"

when deploying with fleet.

The same error shows up when trying to do a helm install with --dry-run so probably Fleet does a --dry-run internally?

I assume we might have to adjust Fleet in a way that it does not do a --dry-run or change the way it does the deployment to allow CRDs to be deployed as part of the helm chart, too.

[StrongMonkey]

This might be the duplicate issue of #415 which should already be fixed. Should be available to test in fleet v0.3.6-rc5.

[Martin-Weiss]

This might be the duplicate issue of #415 which should already be fixed. Should be available to test in fleet v0.3.6-rc5.

We are on Rancher 2.5.8 and 2.5.9 - so do I get it right that we will only get this addressed in 2.6.0?

[StrongMonkey]

@Martin-Weiss I think we are also planning to get v0.3.6 available on v2.5.x.

[Martin-Weiss]

@Martin-Weiss I think we are also planning to get v0.3.6 available on v2.5.x.

Thanks - any idea for a timeline?

[StrongMonkey]

It will be on 2.5.10 if it happens.

[thehejik]

Tested on rancher/rancher:master-head 94bca99

I was able reproduce the issue by helm and --dry-run:

$ git clone postgres-operator
$ cd postgres-operator/charts/postgres-operator
$ helm install postgres-operator . --dry-run
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "OperatorConfiguration" in version "acid.zalan.do/v1"

And on attempt over fleet it worked, this is what I did:

• Dashboard -> Continuous Delivery (fleet)
• Add a repo https://github.com/zalando/postgres-operator, conf
• configure path: charts/postgres-operator
• Select All Clusters in Workspace (I have 2 downstream clusters)
• Click Create button

The repo has been deployed successfully. I also saw the same Error message but it disappeared in few seconds and now the repo is Active:

Close, works as expected.