Our current release process requires us to use an out-of-band process for generating our k8s manifests at the time of deployment. We then use the same custom remote manifest script for each of the services we end up deploying. This leads to a lot of duplication across each of our services, when really the only thing that's different is the name/identifier.

It would be nice if we could write the custom remote manifest once and a mechanism to apply that to any harness service definition as needed.