NO-JIRA: bump library-go and use default UnhealthyPodEvictionPolicy

[atiratree]

etcd should use a default UnhealthyPodEvictionPolicy behavior corresponding to the
IfHealthyBudget policy. This policy achieves the least amount of disruption, as it
does not allow eviction when multiple etcd pods do not report readiness.
This can block node drain/maintenance. The cluster administrator should then
analyze these pods and decide which one to bring down manually.

As opposed to for example to kube-apiserver that can use more permissive eviction policy: openshift/cluster-kube-apiserver-operator#1579

[atiratree]

/retest

[atiratree]

/retest

[atiratree]

/retest

[atiratree]

/retest

[Elbehery]

/retest

[Elbehery]

cc @hasbro17 @dusk125

[ingvagabund]

/retest-required

[dusk125]

/retest-required
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, dusk125

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 [dusk125]

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

[dusk125]

This test is being made optional openshift/release#47252
/override ci/prow/e2e-gcp-qe-no-capabilities

[openshift-ci]

@dusk125: Overrode contexts on behalf of dusk125: ci/prow/e2e-gcp-qe-no-capabilities

In response to this:

This test is being made optional openshift/release#47252
/override ci/prow/e2e-gcp-qe-no-capabilities

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/test-infra repository.

[ingvagabund]

/retitle NO-JIRA: bump library-go and use default UnhealthyPodEvictionPolicy

This PR bumps library-go only. The change under pkg/operator/starter.go reflects the new API which is no-op for this operator.

[openshift-ci-robot]

@atiratree: This pull request explicitly references no jira issue.

In response to this:

etcd should use a default UnhealthyPodEvictionPolicy behavior corresponding to the
IfHealthyBudget policy. This policy achieves the least amount of disruption, as it
does not allow eviction when multiple etcd pods do not report readiness.
This can block node drain/maintenance. The cluster administrator should then
analyze these pods and decide which one to bring down manually.

As opposed to for example to kube-apiserver that can use more permissive eviction policy: openshift/cluster-kube-apiserver-operator#1579

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 9e38f4d and 2 for PR HEAD 647af2f in total

[openshift-ci]

@atiratree: 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/e2e-aws-etcd-recovery	647af2f	link	false	/test e2e-aws-etcd-recovery

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/test-infra repository. I understand the commands that are listed here.

[ingvagabund]

/retest-required

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-etcd-operator-container-v4.16.0-202401100232.p0.ga13dff1.assembly.stream for distgit cluster-etcd-operator.
All builds following this will include this PR.