Deprecate GlusterFS in-tree driver in 1.25 release

[humblec]

Enhancement Description

• One-line enhancement description (can be used as a release note): Deprecate GlusterFS in-tree driver in 1.25 release
• Kubernetes Enhancement Proposal: deprecate GlusterFS plugin from available in-tree drivers. kubernetes#111485
• kubernetes/enhancements file; if none yet, link to PR -
• Discussion Link: https://groups.google.com/g/kubernetes-sig-architecture/c/DZFPPf105iE/m/QgGrKZcKBAAJ
• Primary contact (assignee): @humblec
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone):
  • deprecation release target (x.y): 1.25
  • removal release target (x.y): 1.26
  • Stable release target (x.y):

Additional Ref #

[humblec]

/sig storage

[humblec]

CC @sftim @xing-yang

[cici37]

HI, Following discussion in Slack the release team has APPROVED this exception request. Your updated deadline to make any changes to your KEP is 18:00 PST Thursday 4th August 2022

[cathchu]

Hello @humblec 👋, 1.25 Release Docs shadow here.

This enhancement is marked as ‘Unknown’ for Docs PR 1.25 release. Are docs required for this Enhancement?

If so, please follow the steps detailed in the documentation to open a PR against dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by August 4.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

[humblec]

@cathchu kubernetes/website#35464 covers the doc part of it.. I have also requested to add this in deprecation blog via kubernetes/website#35426

[humblec]

HI, Following discussion in Slack the release team has APPROVED this exception request. Your updated deadline to make any changes to your KEP is 18:00 PST Thursday 4th August 2022

Thanks @cici37 👍

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.