-
Notifications
You must be signed in to change notification settings - Fork 266
make deploy failed: The CustomResourceDefinition "flinkclusters.flinkoperator.k8s.io" is invalid #266
Comments
The operator has problem with k8s 1.18, we will fix it. As a work around, you might use a lower version. |
Related info: SeldonIO/seldon-core#1675 (comment) |
Anything I can do to help fix this? I can't really downgrade my Kubernetes on premise cluster and I would really like to give the operator a try. |
As a temporary workaround, the crd will deploy (on 1.18 in my case) by removing the instances of |
I actually tried something like that (I added protocol to the required properties) and the deploy worked but I am now stuck with the Server-side apply problems (The FlinkCluster "beam-flink-cluster" is invalid: metadata.managedFields.fieldsType: Invalid value: "": must be |
If you must use k8s 1.18, it seems that you can avoid this problem by changing controller-gen version 0.2.4 in Makefile as a workaround. |
I confirm switching to controller-gen 0.2.4 functions as a workaround for this issue. |
Thanks for the suggested workaound, Saved my time while setting up the operator for first time i changed following line (60) in Make file and it worked |
i got the similar problem when deploying the operator to v1.18 with the yaml file,is it also because of the k8s verson ? and how can i help to fix this?
|
Did you tried changing here https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/blob/master/Makefile#L65 and did For |
I did othing to change,just follow the guide https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/blob/master/helm-chart/flink-operator/README.md#installing-the-chart to deploy. |
According this issue GoogleCloudPlatform#266
what changes are required for folks like me who are leveraging the helm chart to deploy this on a 1.18 server ? |
Getting the same error even after trying the workarounds:
|
Failed to deploy the operator on my minikube cluster (v1.18.2):
make deply
error log:The text was updated successfully, but these errors were encountered: