Bug: Some ingresses are not replaced when service wakes up

[col]

I've been implementing Snorlax in our non-prod environment over the last few weeks. Unfortunately it appears to be a bit flakey. When a services wakes, up the ingress if often left pointing the the Snorlax wake server service rather than reverting to it's original setup. The Snorlax wake server service does get removed though so when I try to reach my service I can 503 response.

I have not been able find any errors in the Snorlax operator logs that would help debug what it going on.

I'm using the latest release v0.7.0

[col]

Ok, it looks like this was caused by the Ingress copy ConfigMap containing reference to the Snorlax wake server service instead of the real service. The question now is, how did it end up in this state and how can I avoid it happening again?

Can I get a bit of insight into how Snorlax works to help me debug this?

At what point are the Ingress copy ConfigMaps created and when are they updated?