You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(fix) List catalogsource using client, instead of referring to cache
Using the information in the resolver cache to list the available catalogsources
leads to the very common and widely known problem of using caches: invalid data
due to a stale cache.
This has showed up multiple times in production environments over the years, manifesting
itself in the form of the all subscriptions in a namespace being transitioned into an error
state when a Catalogsource that the cache claims to exist, has actually been deleted from the
cluster, but the cache was not updated.
The Subscriptions are transitioned to an error state because of the deleted catalogsource
with the follwing error message:
"message": "failed to populate resolver cache from source <deleted-catalogsource>: failed to list
bundles: rpc error: code = Unavailable desc = connection error: desc = \"transport:
Error while dialing dial tcp: lookup <deleted-catalogsource>.<ns>.svc on 172.....: no such host\"",
"reason": "ErrorPreventedResolution",
"status": "True",
"type": "ResolutionFailed"
This PR switches the information lookup from the cache, to using a client to list the CatalogSources
present in the cluster.
0 commit comments