IssueTracker

We usually use the below gcloud command to query the asset-inventory to pull the updated list. The issue we are seeing apparently showing the IP of an older cluster not the current:

gcloud asset search-all-resources \

--scope='organizations/[organization-id]' \

--asset-types='container.googleapis.com/Cluster' \

--format json

According to the documentation Data freshness in the Cloud Asset API is on a best-effort basis. While almost all asset updates will be available to clients in minutes.

It seems the Cloud Asset API isn’t a suitable solution for how we were using it – moderate latency (in the order of minutes) would be fine, but for it to just "lose" some updates, because sometimes take longer time to get the updated data because the data freshness fail, and raise a support ticket is needed to get an urgent update, being not reliable for automated processes.

How this might work:

Improve the data freshness in the asset-inventory system in order to have the GKE cluster endpoint updated and prevent the Cloud Asset API from getting stuck and don't show the current information.