Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Section regarding Portworx in-tree plugin deprecation should be removed from blog #34144

Closed
xing-yang opened this issue Jun 6, 2022 · 7 comments · Fixed by #36081
Closed
Assignees
Labels
area/blog Issues or PRs related to the Kubernetes Blog subproject kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@xing-yang
Copy link
Contributor

xing-yang commented Jun 6, 2022

This is a Bug Report

Problem:
In the blog https://kubernetes.io/blog/2022/04/07/upcoming-changes-in-kubernetes-1-24/, there is a paragraph about Portworx CSI driver migration. This was because Portworx was originally targeting Beta in 1.24 so the in-tree plugin will be deprecated as a result of that. However, Portworx CSI migration didn't make it, so it stayed in Alpha in 1.24. They will try to target Beta again in 1.25.

So the following paragraph should be removed from the 1.24 blog.

In-tree provisioner to CSI driver migration: This applies to a number of in-tree plugins, including [Portworx](https://github.com/kubernetes/enhancements/issues/2589). Refer to the [In-tree Storage Plugin to CSI Migration Design Doc](https://github.com/kubernetes/design-proposals-archive/blob/main/storage/csi-migration.md#background-and-motivations) for more information.

Proposed Solution:

Page to Update:
https://kubernetes.io/...

@xing-yang xing-yang added the kind/bug Categorizes issue or PR as related to a bug. label Jun 6, 2022
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 6, 2022
@k8s-ci-robot
Copy link
Contributor

@xing-yang: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

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.

@sftim
Copy link
Contributor

sftim commented Jun 6, 2022

/area blog
/sig release

We should not remove that paragraph; however, we can follow it with a clarifying statement, and we can strike through text that is no longer correct.

@k8s-ci-robot k8s-ci-robot added area/blog Issues or PRs related to the Kubernetes Blog subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Jun 6, 2022
@humblec
Copy link
Contributor

humblec commented Jun 6, 2022

@sftim I dont know its worth to mention, along with portworx , rbd was also in the same state, that said, both entered alpha in 1.23 and then tried beta in 1.24 , but both didnt make it.. I am not sure how only one landed in first place though.

@nitishfy
Copy link
Member

nitishfy commented Jun 6, 2022

/assign

@sftim
Copy link
Contributor

sftim commented Jun 6, 2022

/retitle Section regarding Portworx in-tree plugin deprecation should be removed from blog

@k8s-ci-robot k8s-ci-robot changed the title Section regarding Portwork in-tree plugin deprecation should be removed from blog Section regarding Portworx in-tree plugin deprecation should be removed from blog Jun 6, 2022
@nitishfy
Copy link
Member

nitishfy commented Jun 7, 2022

@sftim what according to you should be added more?

@nitishfy
Copy link
Member

Hi! @xing-yang , according to you what changes should be done to the file so that I can have a basic idea regarding the same if we both are inclining at same thought?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/blog Issues or PRs related to the Kubernetes Blog subproject kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
5 participants