panic: runtime error: during discovery (rate limiting issue?)

[mm-weber]

Describe the bug
When creating a new GCP cluster:

This will break the discovery when trying to connect via this:

cnspec shell gcp project <project-name> --discover gke-clusters

To Reproduce
Steps to reproduce the behavior:

1. Create a new GKE cluster from the console
2. Run cnspec shell gcp project <project-name> --discover gke-clusters
3. Note the error

Expected behavior
The discovery should not fail when a GKE cluster is being created.

Screenshots or CLI Output
See above

Desktop (please complete the following information):

installing provider 'gcp' version=11.0.63

Additional context
Add any other context about the problem here.

[mm-weber]

Update

This issue happens when the number of GKE clusters in a project exceeds 1 !
Just tried after the provisioning was complete, the error persisted.

[mm-weber]

Update 2:

Even after deleting one of the two testing clusters, the error seems to persist when trying to discover the cluster left behind.
Could this be a rate-limiting issue?

[vjeffrey]

two problems here:
need to fix threads per core, we're trying to give it a bool right now, it should be:
+ "threadsPerCore": llx.IntDataPtr(cfg.AdvancedMachineFeatures.ThreadsPerCore),

the serviceaccount init from the gke cluster is failing to trigger

[vjeffrey]

the first bit is an easy fix but i am struggling to figure out why on earth the service account init is not triggering, will continue to look

[vjeffrey]

partially resolved with #5135

[vjeffrey]

ok, got it all working with https://github.com/mondoohq/cnquery/compare/vj/fixgke-2?expand=1

feels like im overcomplicating the second commit so ill get back to that tomorrow