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
When you have an API removed from swagger.json it cannot be verified against the API Server, because the normal flow is to check all the deprecated apis from swagger.json and check their existence. If something doesn't exists, we cannot check :(
The solution here is to walk across all the existent resources in the API Server and check if they still exists in swagger.json.
If don't, check if there's some object inside that resource and notify that Object might disappear / stop working in future releases
So the flow will be (using discovery and dynamicclient)
Get all the GroupVersion items
For each GV item, get resources
For each resource, check if its definition exists in the swagger JSON
If that resource doesn't exists in the JSON, check if there're objects inside that Resource
If there're objects, show the objects alerting about the deprecation of that version
alert the user about the nonexistence of that API in the future k8s release
The text was updated successfully, but these errors were encountered:
To the future me:
When you have an API removed from swagger.json it cannot be verified against the API Server, because the normal flow is to check all the deprecated apis from swagger.json and check their existence. If something doesn't exists, we cannot check :(
The solution here is to walk across all the existent resources in the API Server and check if they still exists in swagger.json.
If don't, check if there's some object inside that resource and notify that Object might disappear / stop working in future releases
So the flow will be (using discovery and dynamicclient)
alert the user about the nonexistence of that API in the future k8s release
The text was updated successfully, but these errors were encountered: