Open unixdaddy opened 2 years ago
FWIW, regional clusters seem to work fine.
I've just installed the 0.2.0-preview on a regional gke 1.22.6 cluster and I had to remove it again, as our helm/helmfile deployments run all into timeouts.
Maybe it would be good to have an include list of crd's that you want to use, instead of installing all 400 by default.
Hi @hprotzek https://github.com/crossplane/crossplane/pull/2918 is where we document these issues, feel free to take a look at. https://github.com/crossplane/crossplane/issues/2869 is the issue about selective installation that you can give a thumbs up and/or provide more details.
For the cluster becoming unresponsive, I'd suggest opening a ticket to GKE support team.
What happened?
From slack discussion
Deployed vm instance using crossplane provider-jet-gcp:v0.2.0-preview on GCP using GKE as my crossplane management cluster. Even with GKE 1.23.1, 400+ CRDS meant the API server response was pretty slow
After creating a GKE 1.23.1 cluster and installing the jet provider the system is totally unresponsive for awhile (time for a :tea: )
after awhile the system becomes responsive, however commands to crossplane resources can be slow
@muvaf has explained why
The question is how can the initial unresponsiveness - the install of the 438 CRDs - be mitigated or resolved or accepted.
How can we reproduce it?
Chart Name: crossplane Chart Description: Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume. Chart Version: 1.6.2 Chart Application Version: 1.6.2
Kube Version: v1.23.1-gke.500
kubectl crossplane install provider crossplane/provider-jet-gcp:v0.2.0-preview
kubectl get all -n kube-system Unable to connect to the server: net/http: TLS handshake timeout Unable to connect to the server: net/http: TLS handshake timeout Unable to connect to the server: net/http: TLS handshake timeout Unable to connect to the server: net/http: TLS handshake timeout Unable to connect to the server: net/http: TLS handshake timeout Unable to connect to the server: net/http: TLS handshake timeout
time kubectl get pods -n crossplane-system NAME READY STATUS RESTARTS AGE crossplane-cfb4cb44f-8qqlf 1/1 Running 3 (6m8s ago) 19m crossplane-provider-jet-gcp-b5eb4524318a-7dd4b6fb44-pw8tk 1/1 Running 3 (5m54s ago) 9m31s crossplane-rbac-manager-d9d6c54c7-75lbn 1/1 Running 1 (8m33s ago) 19m
real 1m0.098s user 0m0.059s sys 0m0.027s
time kubectl get pods -n crossplane-system The connection to the server XX.XX.XX.XX was refused - did you specify the right host or port?
real 0m37.761s user 0m0.052s sys 0m0.019s