-
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
Durable (non-shared) local storage management #121
Comments
I assume this is kubernetes/kubernetes#7562 ? And that kubernetes/kubernetes#30044 is related? |
Yes and yes. Consensus is to see if we can pull together a design at most in 1.5 |
It would be great if we were ready to go at this in 1.6 |
I think we can commit to that. On Mon, Oct 10, 2016 at 9:35 PM, Prashanth B notifications@github.com
|
Yes, I will definitely spend more time on this after this short release Jing On Mon, Oct 10, 2016 at 10:53 PM, Tim Hockin notifications@github.com
|
@msau42 and myself will be tackling this problem in v1.6. The plan is as follows:
@rkouj and @jingxu97 will also be helping with this effort. @msau42 and @vishh will post a high level design proposal before end of Jan `17. |
Please loop me in on the scheduling aspects of this. |
Misread the @vishh comment, let's target 1.7 when this milestone will be open. |
Yeah. A design proposal will be made available anytime now.
…On Fri, Jan 27, 2017 at 5:07 AM, Steve Watt ***@***.***> wrote:
@vishh <https://github.com/vishh> and others. Given that we're already
talking about targeting releases, is there a design proposal for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGvIKLoIavf4pD5a8orh_CATy-s2gVi0ks5rWewXgaJpZM4KR2_S>
.
|
@vishh has this anything to do with sticky empty dir proposal or local storage for statefulset ? I am getting confused which feature is doing what ? There are many things needed for local storage , e.g. 1: local storage support in statefulset 2: local storage volumes which is this one 3: pod should be scheduled in the same node where their data is already available 4: may be moving data to where the pod gets scheduled . It will be good to have one local storage featur which covers all related issues and proposals |
@krmayankk the plan is to cover all supported use cases for local storage. |
@vishh I assume you are not including (4) from @krmayankk's comment? (migrating data between nodes) |
/assign @cofyc |
Adding tracked label to reconcile against https://bit.ly/k8s114-enhancements |
Hey @cofyc @msau42 👋 I'm the v1.14 docs release lead. Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! |
it doesn't sound like there are API changes involved in the 1.14 work. Is that accurate? |
I think API was done long ago. |
Hello, 1.14 enhancement shadow here. Code Freeze is March 7th and all PRs must be merged by then to your issue to make the 1.14 release. What open K/K PRs do you still have that need to merge? Thanks |
The items I listed above here tracks our 1.14 work. |
Hello @msau42 @smarterclayton , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. If this was included as GA in 1.14 lets close this issue. Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly. /milestone clear |
1.14 was GA and any additional enhancements should be tracked as new features. |
@msau42: 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. |
…our_own_vnet Azure: Customer provisioned virtual network & subnets enhancement doc
Automatic merge from submit-queue. Volume topology aware scheduling design Proposal for a smarter scheduler that influences PV binding. Part of kubernetes/enhancements#121 /sig storage /sig scheduling /cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Automatic merge from submit-queue. Volume topology aware scheduling design Proposal for a smarter scheduler that influences PV binding. Part of kubernetes/enhancements#121 /sig storage /sig scheduling /cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Automatic merge from submit-queue. Volume topology aware scheduling design Proposal for a smarter scheduler that influences PV binding. Part of kubernetes/enhancements#121 /sig storage /sig scheduling /cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Automatic merge from submit-queue. Volume topology aware scheduling design Proposal for a smarter scheduler that influences PV binding. Part of kubernetes/enhancements#121 /sig storage /sig scheduling /cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Automatic merge from submit-queue. Volume topology aware scheduling design Proposal for a smarter scheduler that influences PV binding. Part of kubernetes/enhancements#121 /sig storage /sig scheduling /cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Automatic merge from submit-queue. Volume topology aware scheduling design Proposal for a smarter scheduler that influences PV binding. Part of kubernetes/enhancements#121 /sig storage /sig scheduling /cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Feature Description
The text was updated successfully, but these errors were encountered: