Testing of PodDisruptionBudgets makes tnf not working with OCP <= 4.7.x about cnf-certification-test HOT 4 OPEN

@ramperher is this issue still valid?

from cnf-certification-test.

@ramperher doing some clean up - can this be closed or still relevant?

from cnf-certification-test.

@sebrandon1 @mwlinca As OCP 4.7 is EOL, I think this can be closed, but maybe I'd emphazise this and try to include this comment, because this is still valid: Just saying this because, in the docs: https://test-network-function.github.io/cnf-certification-test/test-spec/#cnf-specific-tests, minimum OCP version is supposed to be 4.6.0. Probably it should be increased to 4.8.0. Also, take into account that 4.7 is EOL.

from cnf-certification-test.

Good call, we should probably match up the documentation to what versions of OCP that QE is currently testing against. Honestly I think the only thing tying us to a certain version of OCP/k8s is the compatibility with the k8s golang client and k8s version.

However, the compatibility matrix on the client-go README hasn't been updated in some time so I can't say for certain which features work/don't work with a certain version of k8s/OCP/client-go.

from cnf-certification-test.