[Bug]: Some resources not available with kubectl get ...
(Client.Timeout exceeded while awaiting headers)
#590
Labels
kubectl get ...
(Client.Timeout exceeded while awaiting headers)
#590
Is there an existing issue for this?
Affected Resource(s)
maybe some others
Resource MRs required to reproduce the bug
Subnetwork
Steps to Reproduce
What happened?
I'm trying to deploy Cloud Run service with Direct VPC Access enabled. Working with fresh Crossplane installation. To enable VPC Access Cloud Run needs VPC subnetwork, so I'm trying to create Subnet with Crossplane. When there is no
Subnetwork
manifests present in the clusterkubectl get subnetworks
gives me:which is fine, but if I apply any
Subnetwork
MR to the clusterkubectl get subnetworks
returns error:resource itself is created, but I can't see its status and, which is more concerning, Argo CD can't determine it as well.
I turned on debug log for
upbound-provider-gcp-compute
and sometimes it's throwing bunch of errors like thisnot only for subnets, actually all CRDs of the provider are mentioned
I have other GKE cluster for testing purposes in other GCP project and everything works completely fine there.
Relevant Error Output Snippet
No response
Crossplane Version
1.16.0
Provider Version
1.5.0
Kubernetes Version
v1.29.6-gke.1038001
Kubernetes Distribution
GKE
Additional Info
No response
The text was updated successfully, but these errors were encountered: