CDAP deployment on GKE 1.22 and later versions

Question

I am not able to deploy CDAP onto the GKE version 1.22 + versions.

Getting error Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "CDAPMaster" in version "apiextensions.k8s.io/v1"

https://cdap.atlassian.net/wiki/spaces/DOCS/pages/911179793/Installing+CDAP+on+Kubernetes

Does CDAP only support GKE 1.21 version as we had no issues with that.

Answer 1

I could resolve the deployment issue by using the customresourcedefinition which @gari has shared in the comment. Additionally, for CDAP deployment i had to use below api in GKE 1.22 version.

apiVersion: cdap.cdap.io/v1alpha1 kind: CDAPMaster

Answer 2

Error : INSTALLATION FAILED: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "CDAPMaster" in version "apiextensions.k8s.io/v1" states that your apiextensions.k8s.io/v1 API version of CustomResourceDefinition is no longer supported.

Please refer to Removed API versions in 1.22 for more details.

CDAP Operator is still under active development and has not been extensively tested in production environments. Backward compatibility of the APIs is not guaranteed for alpha releases. Beta versions of previously graduated APIs are removed in 1.22 in favor of the GA version : apiextensions.k8s.io/v1beta1, CustomResourceDefinition.

Steps to be taken to run through the resources that are affected by these removals :

1. You can use the v1 API to retrieve or update existing objects, even if they were created using an older API version. If you defined any custom resources in your cluster, those are still served after you upgrade.

2. If you're using external CustomResourceDefinitions, you can use kubectl convert to translate existing manifests to use the newer API. Because there are some functional differences between beta and stable CustomResourceDefinitions, our advice is to test out each one to make sure it works how you expect after the upgrade.

Also go through the official blog post Kubernetes API and Feature Removals In 1.22 for more information.