We are currently using controller version 0.25.0, which is quite outdated and has been improved on significantly since then. A careful and tested upgrade would be a good idea to stay up to date with security and bug-fix patches.
In addition to that, the helm chart is now embraced in the upstream repo. Using the helm chart would simplify some aspects of upgrade management (upgrades and rollbacks are made quite clear), remove a lot of boilerplate from our yaml, and possibly add a set of settings for local testing in the future. The only changes that would require is:
- installing helm 3 from our repos to the control plane servers
- swapping out the yaml files in puppet with yaml files that are strictly our override values (basically, a values.yaml with a more expressive name)
For PAWS, changing to using the helm chart is even easier, if the ingress controller is made an optional dependency and the values are added to the existing values and secrets yaml files. I will definitely propose a patch for this latter case because it's very easy to not include that in minikube deploy while deploying our setup to PAWS prod.