Value Statement

We want user to be able to configure our controllers more easily.

Definition of Done for Engineering Story Owner (Checklist)

• Ensure all useful parameters on the controller struct (or on other variables in the code) are able to be configured through command line flags or environment variables.
• Ensure all those useful parameters are available at the "top-level" of the helm chart (ie, not nested within other fields)
• Write a test to verify that an AddOnDeploymentConfig can be used to configure at least one of the new options.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.