Find way to capture unintended changes in semantics or api

[iocanel]

The kubernetes-client does try to stay true to semnatic versioning as much as possible (at least for major changes).

Still, there are changes that may untintentionally change things, for example:

• a change in kubernetes/openshift code itself
• a change in the generator code
• an internal change that affects the client behavior.

I am pretty sure that there is tooling out there that could ensure that we capture changes in our public API during CI.

In addition, there might be tools that check the structure of the HTTP requests the client generates under a fixed set of circumstances. Even if they don't we do have our own mocking framework, so we could possibly extract infomration for there.

These are just some ideas we could possibly use to further guard our users.

[manusa]

Relates to: #2518

[maxandersen]

Revapi is what we are looking at in quarkus to do this. For Kubernetes which is much smaller it should be fairly easy to enable.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!