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
It's possible in kubernetes to have different APIs that serve the same resource, like when some thing move from a beta to a regular API. Our sources are only able to find data for one type, and one API version each. So a source that works for v1Pods wouldn't work for v2Pods (just an example). In order to support people that are using older resources, we really should be looking at the possible versions for things and creating additional sources. This would then raise the question of which should we should use. Kube does have APIs that will report which versions of things are available, but more research would be needed to determine how this works exactly and how we should be using it
The text was updated successfully, but these errors were encountered:
It's possible in kubernetes to have different APIs that serve the same resource, like when some thing move from a beta to a regular API. Our sources are only able to find data for one type, and one API version each. So a source that works for
v1
Pods
wouldn't work forv2
Pods
(just an example). In order to support people that are using older resources, we really should be looking at the possible versions for things and creating additional sources. This would then raise the question of which should we should use. Kube does have APIs that will report which versions of things are available, but more research would be needed to determine how this works exactly and how we should be using itThe text was updated successfully, but these errors were encountered: