EQoS: Set force:true for server-side-apply

[tssurya]

- What this PR does and why is it needed

Force: true was not set on EQoS status updates in ovnkube-controller
causes conflicts when trying to patch

- Special notes for reviewers

- How to verify it

- Description for the changelog
Use force:true when doing server side apply

[tssurya]

/assign @pperiyasamy

[coveralls]

coverage: 52.438% (+0.03%) from 52.408%
when pulling dff5dc7 on tssurya:egressqos-status
into 361d573 on ovn-org:master.

[pperiyasamy]

/lgtm

Thanks @tssurya , The EgressQoS CRD is also not yet updated in d/s https://github.com/openshift/cluster-network-operator/blob/master/bindata/network/ovn-kubernetes/common/001-crd.yaml#L433-L435, Can you do that, please ?

[tssurya]

/lgtm

Thanks @tssurya , The EgressQoS CRD is also not yet updated in d/s https://github.com/openshift/cluster-network-operator/blob/master/bindata/network/ovn-kubernetes/common/001-crd.yaml#L433-L435, Can you do that, please ?

oh! woops nice catch :) I thought when we added the RBAC we took care of updating the CRD, yeah will fix that as well as part of same bug

[tssurya]

/lgtm

Thanks @tssurya , The EgressQoS CRD is also not yet updated in d/s https://github.com/openshift/cluster-network-operator/blob/master/bindata/network/ovn-kubernetes/common/001-crd.yaml#L433-L435, Can you do that, please ?

openshift/cluster-network-operator#2362 done!

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-05-04-214435