As of right now it seems the only way to install the routingmanager into a namespace is to do it via the extension (or kubectl apply with changes to the routingmanager.yml file, though this seems to be slightly outdated?). It would be great if there was a way to manage the deployment through a helm chart, this is especially useful for teams that use bridge to kubernetes exclusively to spin up temporary review applications from a pull request context, and don't ever use it locally via the extension.
Another thing that would be extremely helpful alongside the above would be to provide changelogs, and a public list of tags for the routingmanager image.
As of right now it seems the only way to install the routingmanager into a namespace is to do it via the extension (or kubectl apply with changes to the
routingmanager.ymlfile, though this seems to be slightly outdated?). It would be great if there was a way to manage the deployment through a helm chart, this is especially useful for teams that use bridge to kubernetes exclusively to spin up temporary review applications from a pull request context, and don't ever use it locally via the extension.Another thing that would be extremely helpful alongside the above would be to provide changelogs, and a public list of tags for the routingmanager image.