Hi there. Basically, see the subject line. If you’re locally-hosted (rare these days), have you tried breaking-out the SG emailnotifier layer into a separate kubernetes (k8s) deployment?
FWIW it’s totally possible to run “the whole” app as a k8s deployment, or just the API or UI. We run like that right now.
It’s also 100% working to run just the emailnotifier as a docker container, which is as expected since that’s how cloud deployment would work.
But back to k8s… we want to make sure that one-and-only-one emailnotifier layer is running, because duplicate such layers == duplicate emails. Therefore we need a different k8s manifest for one container or pod that includes the email notifier and then all the rest without it.
So I’m trying to make a manifest that only runs the emailnotifier (with replicas=1), not the UI nor API. Unlike the docker-container approach, the k8s pod crashes immediately upon starting up – it seems the expected /var/rails/shotgun/current/config/memcached.yml file isn’t initially present at pod startup and so basically a file-not-found error gets thrown.
I’m considering using a ConfigMap or initContainer to jam the file into place before the emailnotifier layer starts.
Wondering if anyone else has attempted this madness, or just me…