-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
generic ephemeral inline volumes #1698
Comments
Hey there @pohly -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19? In order to have this part of the release:
The current release schedule is:
If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍 Thanks! |
Hey @pohly, I'm following up on my previous update on this Enhancement being part of the Do you happen to have any update on the possiblity of this being included in the release Thanks again for your time and contributions. 🖖 |
1 similar comment
Hey @pohly, I'm following up on my previous update on this Enhancement being part of the Do you happen to have any update on the possiblity of this being included in the release Thanks again for your time and contributions. 🖖 |
@harshanarayana: please track this as a new alpha feature for 1.19. The KEP still needs to be merged, but we already discussed it and should get there soon. |
Hey @pohly, thank you for confirming the inclusion into /milestone v1.19 |
Hey @pohly, Enhancement shadow for the I noticed that the KEP is still in flight. As per the requirements, the KEP should be merged and Please feel free to reach out in case if you need any more information. Regards, Harsha |
Hi @pohly - My name is Zachary, 1.19 Docs shadow. Is this enhancement work planned for 1.19 and does it require any new docs (or modifications to existing docs)? If not, can you please update the 1.19 Enhancement Tracker Sheet, or let me know, I can do it for you :) |
Hey @pohly, I am with the enhancements team for the The code freeze deadline for the Enhancement is Have a wonderful day. 🖖 |
Hi @pohly - Just a reminder that docs placeholder PR against dev-1.19 is due by June 12th. Does this enhancement require any changes to docs? If so, can you update here with a link to the PR once you have it in place? If not, please update the same, so that the tracking sheet can be updated accordingly. Thanks! |
Doc placeholder PR: kubernetes/website#22438 (updated 2020-07-09) I used to have the docs in a combined PR kubernetes/website#21634 but then moved to a separate one. |
Hi, @pohly This is a follow-up to the communication that went out to Thursday, July 9th: Week 13 - Code Freeze
Thursday, July 16th: Week 14 - Docs must be completed and reviewed
Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released
Thursday, August 27th: Week 20 - Release Retrospective You can find the revised Schedule in the sig-release Repo Please let me know if you have any questions. 🖖 |
This comment accidentally had a TODO list for Storage Capacity tracking. The content was moved to #1472 (comment). |
/assign |
TODO before beta:
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
/milestone v1.23 |
Hi @pohly 👋 1.23 Docs shadow here. This enhancement is marked as Needs Docs for the 1.23 release. Please follow the steps detailed in the documentation to open a PR against the Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thanks! |
Final implementation PR for GA: kubernetes/kubernetes#105609 |
Hi @pohly , 1.23 Enhancements Shadow here. Looks like this enhancement's code PR is merged so all good for code freeze on November 16th. Please let me know if there's any other PR besides #105609 I should be aware of. Thanks! |
Here's the PR marking this enhancement as implemented: #1698 However, there is one last task left: remove the feature gate definition from https://github.com/kubernetes/kubernetes/blob/712745cb6755b3a28ca12292b30d138d5f737aa6/pkg/features/kube_features.go#L171-L177 (and also docs?). Does anyone know when that should be done? |
Hi @gnufied @mattsmithdatera , 1.24 Enhancements Lead here. This enhancement is considered graduated to Thanks :) |
Kubernetes deprecation policy says 2 releases for removing a feature gate: https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-a-feature-or-behavior It's also commented in the code: https://github.com/kubernetes/kubernetes/blob/712745cb6755b3a28ca12292b30d138d5f737aa6/pkg/features/kube_features.go#L897 I think you can go ahead and close this. In the past, I have seen PRs where all feature gates are cleaned up for a given release. |
Yes - no need to keep it just for feature gate removal. |
/close |
@pohly: Closing this issue. In response to this:
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. |
Enhancement Description
The current CSI ephemeral inline volume support is designed for CSI drivers that are specifically written for such volumes. The assumption is that such volumes can be created and destroyed quickly on a node together with the pod. Parameters are driver specific.
But ephemeral inline volumes are also useful in combination with traditional storage drivers, for example as temporary scratch space. The goal is to enable ephemeral inline volumes such that:
The text was updated successfully, but these errors were encountered: