promote HonorPVReclaimPolicy to GA

[carlory]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Part of kubernetes/enhancements#2644

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Promoted the feature gate `HonorPVReclaimPolicy` to GA.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/issues/2644

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[carlory]

We can not remove the gated code because the gated code and feature gate must be removed together. It is required by https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/feature-gates.md#ga-features.

I remove feature label and related code from e2e tests because the feature-gate can not be changed by users and the feature label is no longer needed.

the pull-kubernetes-e2e-kind job runs these e2e tests.

[carlory]

/hold
until kep is updated. kubernetes/enhancements#5035
/cc @deepakkinni @xing-yang

[carlory]

/hold cancel
/cc @deepakkinni @xing-yang
the kep is merged.

[xing-yang]

/assign @deepakkinni

[carlory]

/test pull-kubernetes-cmd

[xing-yang]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b4f5ef5f7a6d346552347cd2f4d6e9d5779db0df

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: carlory, xing-yang

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:

• pkg/controller/volume/OWNERS [xing-yang]
• pkg/features/OWNERS [xing-yang]
• test/e2e/feature/OWNERS [xing-yang]
• test/e2e/storage/OWNERS [xing-yang]
• test/featuregates_linter/test_data/OWNERS [xing-yang]

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

[carlory]

/retest

[carlory]

@xing-yang rebased, please review it again. thanks.

[carlory]

/test pull-kubernetes-unit

[deepakkinni]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 5bc1f5f589f76c6ad43812cc1f88a067bb404d56

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest