Cluster operator installation issue

[charansaip]

Hi All, & @scholzj
we are getting below error while we installing cluster operator. can anyone what is the issue in this.

i tried multiple times to install others are getting created but below some are failing.

t apply -f ./install/cluster-operator -n kafka
serviceaccount/strimzi-cluster-operator created
clusterrole.rbac.authorization.k8s.io/strimzi-cluster-operator-namespaced created
rolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator created
clusterrole.rbac.authorization.k8s.io/strimzi-cluster-operator-global created
clusterrolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator created
clusterrole.rbac.authorization.k8s.io/strimzi-cluster-operator-leader-election created
rolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator-leader-election created
clusterrole.rbac.authorization.k8s.io/strimzi-cluster-operator-watched created
rolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator-watched created
clusterrole.rbac.authorization.k8s.io/strimzi-kafka-broker created
clusterrolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator-kafka-broker-delegation created
clusterrole.rbac.authorization.k8s.io/strimzi-entity-operator created
rolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator-entity-operator-delegation created
clusterrole.rbac.authorization.k8s.io/strimzi-kafka-client created
clusterrolebinding.rbac.authorization.k8s.io/strimzi-cluster-operator-kafka-client-delegation created
customresourcedefinition.apiextensions.k8s.io/strimzipodsets.core.strimzi.io created
Warning: Detected changes to resource kafkatopics.kafka.strimzi.io which is currently being deleted.
customresourcedefinition.apiextensions.k8s.io/kafkatopics.kafka.strimzi.io unchanged
customresourcedefinition.apiextensions.k8s.io/kafkausers.kafka.strimzi.io created
customresourcedefinition.apiextensions.k8s.io/kafkaconnectors.kafka.strimzi.io created
customresourcedefinition.apiextensions.k8s.io/kafkarebalances.kafka.strimzi.io created
configmap/strimzi-cluster-operator created
deployment.apps/strimzi-cluster-operator created
error when creating "install/cluster-operator/040-Crd-kafka.yaml": Post "https://10.1.2.5:443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?fieldManager=kubectl-client-side-apply&fieldValidation=Strict": http2: client connection lost
error when creating "install/cluster-operator/041-Crd-kafkaconnect.yaml": Post "https://10.1.2.5:443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?fieldManager=kubectl-client-side-apply&fieldValidation=Strict": http2: client connection lost
error when creating "install/cluster-operator/045-Crd-kafkanodepool.yaml": Post "https://10.1.2.5:443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?fieldManager=kubectl-client-side-apply&fieldValidation=Strict": http2: client connection lost
error when creating "install/cluster-operator/046-Crd-kafkabridge.yaml": Post "https://10.1.2.5:443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?fieldManager=kubectl-client-side-apply&fieldValidation=Strict": http2: client connection lost
error when creating "install/cluster-operator/048-Crd-kafkamirrormaker2.yaml": Post "https://10.1.2.5:443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?fieldManager=kubectl-client-side-apply&fieldValidation=Strict": http2: client connection lost

[im-konge]

I don't think that you need to tag Jakub directly in discussions, somebody from maintainers will pick this up.

Do you have CRDs from "before"?

[charansaip]

I have cleared and applied one of the crd 043-Crd-kafkatopic.yaml same errorr for big yaml files.
small files able to get deploy

[im-konge]

Hmm out of curiosity, do you have kubectl client updated to latest version? I saw that it may cause some issues with older versions of the client.

[im-konge]

What I read is (and what you can try):

• use kubectl create instead of apply which should be better (there is no merge, calculation of patch)
• use kubectl apply -f ... --validate=false for the CRDs
• I saw also --server-side=true to leave the "apply" on server and not client.

[im-konge]

But first I would check if the kubeclient is up to date

[scholzj]

Could be some unresponsive Kubernetes Webhook or something. While I never saw this with kubectl and Crds, the way similar issue shows up with Pods for example is pretty similar.