This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Device allocator should not use reserved dev names.
According to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html, on HVM instances, sda1 and xvda are reserved for root partition. Also, the available block device range for xvd follow "/dev/xvd[b-c][a-z]" pattern. However commit 1ace946 violates the reserved device names and the naming logic. This causes volume attachment issues. For example, for instances where /dev/xvda is root partition, the driver tries to create a new device with the same reserved name. This change fixes the issue. Testing: Deployed Kube 1.14 cluster. Update manifest.yaml with canary images for sidecards and new names for API resources. Tested new plugin and created sc, pvc (pv) and pod. Volume attaches to node successfully. New device attached is "/dev/xvdba" as expected. Pod mounts volume and runs fine. Issue kubernetes-sigs#292 Signed-off-by: Anusha Ragunathan <anusha.ragunathan@docker.com>
- Loading branch information