ETCD-593: Enable experimental-stop-grpc-service-on-defrag

[Elbehery]

This PR enable --experimental-stop-grpc-service-on-defrag on OCP/Etcd.

cc @openshift/openshift-team-etcd

[openshift-ci-robot]

@Elbehery: This pull request references ETCD-593 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

In response to this:

This PR enable --experimental-stop-grpc-service-on-defrag on OCP/Etcd.

cc @openshift/openshift-team-etcd

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.

[dusk125]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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

[hasbro17]

/hold

We need to test and validate whether this flag is actually stopping grpc on the degraded member or if we need to enable something on the etcd client side as well.
kubernetes/kubernetes#124787

[openshift-ci]

@Elbehery: 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-gcp-qe-no-capabilities	b42f48e	link	false	/test e2e-gcp-qe-no-capabilities
ci/prow/e2e-operator-fips	b42f48e	link	false	/test e2e-operator-fips
ci/prow/e2e-aws-etcd-recovery	b42f48e	link	false	/test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-etcd-scaling	b42f48e	link	unknown	/test e2e-aws-ovn-etcd-scaling

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

[dusk125]

/remove-lifecycle stale