Story (Required)

As a Red Hat engineer trying to support Shared Resource CSI driver I want the node directory for Secret/ConfigMap storage to be customizable so that the GA version of the driver can be deployed alongside the Tech Preview version of the driver.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

The Shared Resource CSI driver currently hard-codes the directory where Secret and ConfigMap data is stored on the host node. This directory needs to be customizable so that we can change it for the GA version of the driver.

Out of scope

<Defines what is not included in this story>

TBD

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

TBD based on refinement.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

• Directory for storing resource data can be changed through a tunable deployment option (ex: environment variable, setting in a ConfigMap/file, etc.)
• Functionality of the driver does not break/regress (CI tests pass)

INVEST Checklist

• Dependencies identified
• Blockers noted and expected delivery timelines set
• Design is implementable
• Acceptance criteria agreed upon
• Story estimated

Legend

• Unknown
• Verified
• Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met