Deprecated resource being shown in multiple API groups about kubepug HOT 6 CLOSED

I should also mention that some of the deprecated resources being returned were in fact created using the latest api version (e.g. apps/v1 for Deployments) but are still shown as deprecated (e.g. extensions/v1beta1 for Deployments) by kubepug.

Seems like the same issue related to how kubepug is requesting the resource and how the k8s api server marshalls between api versions depending on the client's request.

from kubepug.

@codescalar tks for raising this issue!

I'll take a look during this week and the next. The program makes a map of all existing objects in the current swagger and checks which have the 'deprecated' text in their description, trying to get them and so yes, this might happen. Didn't realize that the API could return all of them even if the stable object also exists :)

I'll figure out a way to correlate them and if the object exists both in the stable and the deprecated API remove it from the output :)

Thank you!

from kubepug.

from kubepug.

Hey @codescalar 👋

Just passing here to let you know that I didn't forgot about this. I was refactoring the whole thing here to allow input files and then dealing with this also became easier :)

I'll probably solve this next weekend.

Thank you

from kubepug.

Thanks @rikatz!

from kubepug.

Well, the guessing here is pretty "hard" as I need to cross between each deprecated object and if it exists in some different API :/

I'm thinking about using the discovery library to feed the API with another struct containing all the preferred names and when something from swagger.json is found, check if there's that same resource name as an stable version.

The final movement is to check if the list length of objects containing the deprecated objects is the same length of the list of objects with the maybe preferred name and assume everything is fine :)

Let me see if this works, will need some testing here because IMO it's worst having a false negative than a false positive in this case :)

from kubepug.