Error while installing consul v1.9.1 and v1.8.2

[Shreyas220]

Current Behavior

Currently, we are not able to install consul service mesh using the adapter, here are the logs

{"app":"consul-adapter","level":"info","msg":"installing Consul Connect v1.9.1: unsecured, 1 server, suitable for local exploration","time":"2021-10-07T20:22:19+05:30"}
{"app":"consul-adapter","code":"1000","level":"error","msg":"","probable-cause":"","severity":2,"short-description":"Error applying operation.unable to build kubernetes objects from release manifest: unable to recognize \"\": no matches for kind \"CustomResourceDefinition\" in version \"apiextensions.k8s.io/v1beta1\"","suggested-remediation":"","time":"2021-10-07T20:22:20+05:30"}

The error is
Error applying operation.unable to build kubernetes objects from release manifest: unable to recognize \"\": no matches for kind \"CustomResourceDefinition\" in version \"apiextensions.k8s.io/v1beta1\""

Screenshots/Logs

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

[mgfeller]

Answering a Slack-question ("Michael Gfeller do you get this as well when deploying Consul?") from @leecalcote here:

@leecalcote No, I didn't get this as far as I can remember from when I tested last, which was for v0.6.0 two weeks or so ago.
Which K8s version are you using? The error message in the issue looks like one of the ones I got too, related to the version of Kubernetes used (for Istio which I used to test first with afaicr). I used v1.20.5 in the end. I think I was trying v1.22.1 where it did not work (the api version for crd's is apiextensions.k8s.io/v1 there).
There are end-to-end tests in the GitHub workflow, they were ok not so long ago until golangci-lint started failing, as a consequence of which the end-to-end tests are not executed, unfortunately. (Note to self too...).

// @Shreyas220 @iamsdas

[Shreyas220]

NAMESPACE     NAME                                                              READY   STATUS    RESTARTS   AGE
default       consul-consul-connect-injector-webhook-deployment-69cb9745kx997   1/1     Running   0          2m59s
default       consul-consul-controller-57fb5759f7-9p2cs                         1/1     Running   0          2m59s
default       consul-consul-hdkc2                                               1/1     Running   0          2m59s
default       consul-consul-server-0                                            1/1     Running   0          2m58s
default       consul-consul-webhook-cert-manager-7d59b9f4f5-8fmpf               1/1     Running   0          2m59s

Tested it on v1.21.0
I think this problem exists only for the latest version (even for nginx adapter)

[yash37158]

Does this error still exist
?

[acald-creator]

bump, need to check into this to make sure that this issue isn't occurring