Turbonomic Targets and General Configurations as YAML

I have recently experienced issues at a customer that rotates credentials, api keys or access keys to endpoints or targets and have failed to update Turbo automatically because it is not baked into any operational process. Now the first thing that comes to mind is a simple question of why they don’t have this step in the standard procedure for updating target credentials. Short answer is that it will happen but the project is still ongoing so they aren’t there yet. However, this isn’t the point of this idea.

Given that we run on Kubernetes natively, the use of Custom Resources to automatically import target configurations and secrets for importing license keys or target credentials would be veru useful for standing up Turbonomic without the manual effort of configuring the license and targets manually. Having installed, uninstalled, reconfigured, reset, broken and fixed turbo many times, the most cumbersome task is to add all of the targets back into a clean install or worry about the fact I don’t use tbutil to back it up and restore on a clean instance. I think more use of YAML to determine consistent turbo configuration would make installation and configuration tasks easier, as well as a little less operational overhead, not to mention easier integration with GitOps tooling and methodologies.