Update network operator status for IPsec

[yuvalk]

This commit updates network operator progressing condition for
rolling out IPsec daemonset for cluster. It reflects appropriate
status for network cluster operator which would make
openshift-install to exit gracefully after installing all of IPsec
components for the cluster.

Signed-off-by: Periyasamy Palanisamy [email protected]

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yuvalk
Once this PR has been reviewed and has the lgtm label, please assign knobunc for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

@yuvalk: The following tests 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/e2e-network-mtu-migration-ovn-ipv6	ad8f66d	link	false	/test e2e-network-mtu-migration-ovn-ipv6
ci/prow/security	ad8f66d	link	false	/test security
ci/prow/4.15-upgrade-from-stable-4.14-e2e-azure-ovn-upgrade	ad8f66d	link	false	/test 4.15-upgrade-from-stable-4.14-e2e-azure-ovn-upgrade
ci/prow/4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade	ad8f66d	link	false	/test 4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
ci/prow/e2e-network-mtu-migration-ovn-ipv4	ad8f66d	link	false	/test e2e-network-mtu-migration-ovn-ipv4
ci/prow/e2e-aws-hypershift-ovn-kubevirt	ad8f66d	link	false	/test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec	ad8f66d	link	false	/test e2e-metal-ipi-ovn-ipv6-ipsec
ci/prow/e2e-metal-ipi-ovn-ipv6	ad8f66d	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/unit	ad8f66d	link	true	/test unit
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	ad8f66d	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/verify	ad8f66d	link	true	/test verify
ci/prow/lint	ad8f66d	link	true	/test lint
ci/prow/4.15-upgrade-from-stable-4.14-e2e-gcp-ovn-upgrade	ad8f66d	link	false	/test 4.15-upgrade-from-stable-4.14-e2e-gcp-ovn-upgrade
ci/prow/e2e-vsphere-ovn	ad8f66d	link	false	/test e2e-vsphere-ovn

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.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale