Enhancements: CSI Cluster Registration Mechanism

[saad-ali]

Feature Description

• One-line feature description (can be used as a release note): Introduce the ability for a CSI driver (optionally) to register it self with the Kubernetes API to:
  
  
  
  • Make it easy for end users to discover CSI drivers installed on their cluster.
  
  
  • Allow CSI drivers to customize how Kubernetes interacts with them (e.g. skip attach operation, etc.)
  
  
• Primary contact (assignee): @saad-ali, @jsafrane
• Responsible SIGs: /sig storage
• Design proposal link (community repo): New: https://github.com/kubernetes/features/issues/594 Old: Google doc
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @thockin
• Approver (likely from SIG/area to which feature belongs): @thockin
• Feature target (which target equals to which milestone):
  
  
  
  • Alpha release target (x.y): 1.12
  
  
  • Beta release target (x.y): 1.14
  
  
  • Stable release target (x.y): 1.15
  
  

[justaugustus]

Thanks for the update! This has been added to the 1.12 Tracking sheet.

/assign @saad-ali @jsafrane

[zparnold]

Hey there! @saad-ali I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

[saad-ali]

These objects and registry are designed for CSI drivers authors. No documentation changes needed on kubernetes/website. Changes will be added to kubernetes-csi

[claurence]

Kubernetes 1.13 is going to be a 'stable' release since the cycle is only 10 weeks. We encourage no big alpha features and only consider adding this feature if you have a high level of confidence it will make code slush by 11/09. Are there plans for this enhancement to graduate to alpha/beta/stable within the 1.13 release cycle? If not, can you please remove it from the 1.12 milestone or add it to 1.13?

We are also now encouraging that every new enhancement aligns with a KEP. If a KEP has been created, please link to it in the original post. Please take the opportunity to develop a KEP

[kacole2]

@saad-ali, @jsafrane just checking in from @claurence's post to see if this should be included for tracking. thanks!

[kacole2]

/milestone v1.13

[spiffxp]

@kacole2 this is listed as "stable" on the spreadsheet, looks like it should be alpha?

[kacole2]

@saad-ali can you give an update on the feasibility of this making v1.13 milestone? Enhancements freeze is tomorrow COB. Was the https://github.com/kubernetes/kubernetes/pull/67803 merge for 1.12? And should this be properly tracked as beta now? The only PR i'm seeing in k/k is https://github.com/kubernetes/kubernetes/pull/69462 which is a backfill of tests. If you could tell us what work is being done and if this is going to make the freeze dates for 1.13 (and any associating PRs) that would be great so we can continue to track or drop. thanks!

[saad-ali]

This feature is part of 1.12 and is available as alpha (kubernetes/kubernetes#67803 in 1.12).

We are planning on moving it to beta this release, 1.13.

@jsafrane is working on it for this quarter. Stay tuned for some PRs.

[kacole2]

thanks for the updates @saad-ali

[claurence]

@saad-ali - Is there any work needed left to make this feature beta for 1.13? As an FYI Code slush is 11/9 and Code freeze is 11/15

[kacole2]

@jsafrane are there any PRs we should be tracking as we approach slush? kubernetes/kubernetes#69462 and any others?

[AishSundar]

@jsafrane We are fast approaching Code freeze for 1.13 (11/6). I see kubernetes/kubernetes#69462 is still in active review. I also see atleast 3 more PRs referenced in kubernetes/kubernetes#69462? Are you confident of wrangling this by Wednesday this week giving us a couple of days to watch CI? If not please work with the release team to move this out to 1.14 sooner than later. thanks.

[kacole2]

@jsafrane @hoegaarden @vladimirvivien There hasn't been any progress on kubernetes/kubernetes#69462 in a long time. Should we punt this out to 1.14?

[msau42]

PR to add a CRD installation mechanism: https://github.com/kubernetes/kubernetes/pull/70780/

I just discussed with @saad-ali and @davidz627 and we decided we're going to keep this feature in alpha for this release. We want to focus on CSI GA instead.

[msau42]

These are the tasks we need to do to go to beta:

• [ ] Update known deployment tools to enable the CSI CRD install addon
• [ ] Update addon to install v1beta1 CRDs (chicken and egg with kubernetes/kubernetes#70367?)

[AishSundar]

@kacole2 to move this out of 1.13 for Beta. Thanks

[AishSundar]

@tfogo, @marpaia and @kbarnard10 to remove it from their updates respectively

[kacole2]

/milestone clear

[claurence]

@saad-ali @jsafrane Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP

[jsafrane]

@claurence, yes, we plan to move it to GA.

[claurence]

Thanks @jsafrane - any open PRs for this issue that we should track on the sheet?

[claurence]

@jsafrane great - do y'all have a KEP for this issue? We want all issues to have a KEP by enhancements freeze. Also are there any PRs we should track?

[claurence]

@jsafrane checking on a KEP for this issue - is there a PR open for a KEP?

[msau42]

I discussed with @saad-ali and I don't think this needs to be a separate issue. This is defining a CRD that is used by two features:

• Pass pod info to mount: https://github.com/kubernetes/enhancements/issues/603
• Skip attach: https://github.com/kubernetes/enhancements/issues/770

The actual CRD installation mechanism is tracked by: https://github.com/kubernetes/enhancements/issues/615

[spiffxp]

/milestone clear