Pass Pod information in CSI calls

[jsafrane]

Feature Description

• One-line feature description (can be used as a release note): CSI driver may opt-in to receive information about Pod that requested a volume in NodePublish request.

• Primary contact (assignee): @jsafrane

• Responsible SIGs: @kubernetes/sig-storage-feature-requests @kubernetes/sig-node-feature-requests

• Design proposal link (community repo): CSI: send pod information in NodePublishVolumeRequest community#2439

• Link to e2e and/or unit tests: TBD

• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @gnufied @msau42

• Approver (likely from SIG/area to which feature belongs): @saad-ali

• Feature target (which target equals to which milestone):

  • Alpha release target (x.y): 1.12
  • Beta release target (x.y): 1.13
  • Stable release target (x.y): 1.14

API PRs:

• Make CSINodeInfo and CSIDriver Core APIs kubernetes#73883

Tagging sig-node since it will probably need a new gRPC API in kubelet. Proposal will follow soon. Proposal has been created.

[justaugustus]

Thanks @jsafrane! This has been added to the 1.12 tracking spreadsheet.

/assign @jsafrane
/stage alpha

[zparnold]

Hey there! @jsafrane 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?

[justaugustus]

@jsafrane --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

[msau42]

@childsb @gnufied ^

[kfox1111]

can we pass through volume.Name too? looks like it is already exposed indirectly to the driver by way of the mount path here:
https://github.com/kubernetes/kubernetes/blob/master/pkg/volume/csi/csi_mounter.go#L79
I'd rather use a passed version then parse it out.

[gnufied]

This feature is on track for 1.12. I will open placeholder PR for docs shortly.

@kfox1111 you mean PersistentVolume.Name field?