Set gate SkipReadOnlyValidationGCE to Deprecated

[thockin]

This was created as alpha (off by default) but should probably have used the "Deprecated" setting. Changing it now makes it on by default and still disable-able.

There was no KEP for this - it was considered a "cleanup" which we were being somewhat paranoid about.

Previous versions of Kubernetes on Google Cloud required that workloads (e.g. Deployments, DaemonSets, etc.) which used PersistentDisk volumes were using them in read-only mode.  This validation provided very little value at relatively host implementation cost, and will no longer be validated.  If this is a problem for a specific use-case, please set the `SkipReadOnlyValidationGCE` gate to false to re-enable the validation, and file a kubernetes bug with details. 

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

[thockin]

@kubernetes/release-managers since this did not have a KEP, but does have a gate (bad!!), I can push this to the next release if you prefer. It seems low risk, but those are "famous last words".

[xmudrii]

@thockin @kubernetes/release-team and @kubernetes/release-team-leads will be of a better help here. :)

[thockin]

woops! I let the auto-complete win.

[thockin]

I need an opinion from @kubernetes/release-team and/or @kubernetes/release-team-leads

[pacoxu]

/kind cleanup
/sig apps

ref #114436

• v1.28: remove validation GCE-ism #117531 add the FG

[Priyankasaggu11929]

I need an opinion from https://github.com/orgs/kubernetes/teams/release-team and/or https://github.com/orgs/kubernetes/teams/release-team-leads

Hello @thockin, I've started a slack thread in #sig-release for the discussion.

[dims]

/approve
/lgtm
/hold

/cc @liggitt

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 35c9f9388236dfe660a6e3cee96514844ed083da

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, thockin

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/features/OWNERS [dims,thockin]

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

[Priyankasaggu11929]

Hello @thockin, I've started a slack thread in #sig-release for the discussion.

Per the above discussion, LGTM from 1.29 Release Team too. Thank you!

[thockin]

Comments updated.

[liggitt]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a05f081d67821a7d3fef699e94bb3eb9dab7df29

[tengqm]

Have we updated k8s website for this change?

[pacoxu]

I open kubernetes/website#43574 to sync the status.

[sftim]

Deprecated doesn't sound right to me. We want the feature gate to end up as on by default and locked to true, and we call that “stable” not deprecated.