Restart ovn-controller gracefully on PreStop

[booxter]

Otherwise, it will clean up chassis and other relevant records and cause unnecessary router failovers.

--

This is not a complete solution: the operator will have to indicate to ovn-controller when it's actually ok to clean the chassis records up, with the file created in the container. (Note: I am not sure this is the best way to reflect this request into the pod. Perhaps the pod should instead talk to k8s where this information could be exposed. Another alternative is storing this information somewhere in OVSDB - maybe ovn-controller could even be expanded to read the flag from there and do the right thing?)

Related-Issue: OSPRH-10821

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: booxter

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [booxter]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[booxter]

/retest-required

[karelyatin]

/test ovn-operator-build-deploy-kuttl

[openshift-ci]

@booxter: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ovn-operator-build-deploy-kuttl	53f441f	link	true	/test ovn-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.