Skip to content
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

[release-1.2] Introduce new flag - strict-topology #288

Merged
merged 1 commit into from
Jun 14, 2019

Commits on Jun 6, 2019

  1. Introduce new flag - strict-topology

    With the current implementation, In delayed binding case, CSI driver is offered
    with all nodes topology that are matched with 'selected node' topology keys in
    CreateVolumeRequest.AccessibilityRequirements. So this allows the driver to
    select any node from the passed preferred list to create volume. But this
    results in scheduling failure when the volume created on a node other than
    Kubernetes selected node.
    
    To address this, introduced new flag "--strict-topology', when set, in case of
    delayed binding, the driver is offered with only selected node topology, so that
    driver has to create the volume on this node.
    
    Modified tests so that now every test is run with and without 'strict topology'.
    avalluri committed Jun 6, 2019
    Configuration menu
    Copy the full SHA
    45805aa View commit details
    Browse the repository at this point in the history