Remove the need for install config yaml file in day 2 operations

[neosab]

Remove the dependency on install config yaml for day 2 operations

• [ ] Bug
• [ ] Feature
• [X] Enhancement

Detailed Description

We require the install config yaml file in order to uninstall dispatch or to do any day 2 operations like dispatch manage. It will be hard for users to keep this config file around for a long time.

On top of my head, I think we can store the required install specific data

1. in the Kubernetes cluster (maybe as a separate config map? and storing the location details in config.json)
2. with the CLI config file (usually in ~/.dispatch/config.json)
3. in dispatch database

in that order.

Context

Possible Implementation

Complexity

• [ ] Low - Simple enhancement or bug fix, no architectural changes or refactoring
• [X] Medium - Change requires some thought, but is relatively isolated
• [ ] High - Significant architectural change or large refactor

Impact

• [ ] Low - Annoyance, but does not impact business or functionality
• [X] Medium - Issue can be worked around, but is causing pain
• [ ] High - Blocker

Your Environment

• Dispatch CLI version (or git commit):
• Dispatch Chart version (or image[s] tag):
• Operating System and version:
• Kubernetes version (and distribution):
• Etc (any other useful environmental information):