Add flag to limit checks to next applicable Cluster version.

[des1redState]

Since Clusters can only be upgraded by one minor release at a time, I don't want to see deprecation warnings for versions which are irrelevant to my current upgrade task. For example, if I'm handling a 1.21 > 1.22 upgrade, I only want to see deprecations relevant to that particular upgrade, not all future upgrades. It'd also make automation easier, for example, -e currently returns a non-zero exit code even if the next applicable version has no relevant deprecations.

[dark0dave]

I like this idea.

[stepanstipl]

Thanks for the suggestion @des1redState - we already do this and if we can detect cluster version, we filter out results that aren't relevant¹. If that is not working as expected, please share details.

But I assume the ask is however not to filter non-relevant results, in a sense to keep only API upgrades that can be made, but rather to filter out all non-required upgrades, i.e. only keep the ones that have to be resolved before upgrade to the next version, correct?

Footnotes

1. https://github.com/doitintl/kube-no-trouble/blob/34bff74c89c21f749d2ab38d5c384590ea53d2b6/pkg/printer/filter.go#L7-L21 ↩

[des1redState]

@stepanstipl Well, to be clear, what I'm asking of the tool boils down to:

"You know I'm currently on v1.21, ONLY tell me about deprecations in v1.22"

That doesn't seem to be the case, as currently I'm also presented with deprecations related to v1.25

[stepanstipl]

Ok, thanks for the clarification. Sounds like a useful feature, and should be fairly easy to implement. I would still keep this under a flag, i.e. non-default behaviour, but 👍 .