It has some limitations as the ct install command generates a random release name like otterdog-<hash> and generate a random namespace.
The namespace is configurable, but not the release name.
See helm/chart-testing#310
The otterdog container and ghproxy has configured the initContainers but it doesn't work because the DNS name will be changed from otterdog-[mongodb|valkey].default.svc.cluster.local to something otterdog-<hash>-[mongodb|valkey].default.svc.cluster.local that we cannot predict.
We can investigate a way to catch the name and redefine the initiContainers, which requires research.
It has some limitations as the
ct installcommand generates a random release name likeotterdog-<hash>and generate a random namespace.The namespace is configurable, but not the release name.
See helm/chart-testing#310
The otterdog container and ghproxy has configured the
initContainersbut it doesn't work because the DNS name will be changed fromotterdog-[mongodb|valkey].default.svc.cluster.localto somethingotterdog-<hash>-[mongodb|valkey].default.svc.cluster.localthat we cannot predict.We can investigate a way to catch the name and redefine the initiContainers, which requires research.