Epic Goal*

Remove attach code from kubelet, it should be dead now.

 
Why is this important? (mandatory)

There is quite some code around volume attachment initiated by kubelet instead of kube-controller-manager. All this code is in theory unreachable, because kubelet cannot create VolumeAttachments (confirmation is needed).

We should remove this code to simplify kubelet and kube-controller-manager code.

Scenarios (mandatory) 

1. As Kubernetes/OCP user I don't see any change in volume attachment.
2. As Kubernetes/OCP developer, I can see kubelet's VolumeManager is simpler, because it does not need to handle volume attachment.

 
Dependencies (internal and external) (mandatory)

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - 

Acceptance Criteria (optional)

No regressions both upstream and downstream. We should already have quite decent e2e tests around volume attachment.

Drawbacks or Risk (optional)

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”