Closed mhutter closed 1 year ago
Pointing my finger at #96 and pinging @raffaelespazzoli :)
Thanks for letting me know. It should be fixed now. And yes it's brittle, any suggestions on will to contribute a solution?
Grazie @raffaelespazzoli can, confirm the script is there now.
I don't think any "fix" is needed except maybe automated testing to be sure the script is there before pushing to quay.io. I'm not GH actions expert.
Thanks again
phew all is good what ends good. And yes your point is noted...we should have better automated tests.
Hmm, my initial idea was to use tagged images in those containers as well, but this would currently mean runnning a very outdated image.
But some automated testing before pushing would be nice!
at the moment we only test the deployment of the operator with helm. It's the only thing we were able to automate across all of the operators we maintain. Contributions in this space, even operator-specific contributions, are welcome
Observed behavior
All Keepalived containers created by the operator are in InitCrashLoopBackoff with the following error message in the log of the
config-setup
init container:As a result, all managed IPs (and hence all applications on the cluster) are unreachable.
Cause
The latest version of
quay.io/redhat-cop/keepalived-operator:latest
is missing the notify scripts used in the init container as well as theconfig-reloader
container of the generated keepalived Daemonsets.This is a problem because
quay.io/redhat-cop/keepalived-operator:latest
Always
Workaround
quay.io/redhat-cop/keepalived-operator:v1.4.2
insteadThis is very brittle as the deployment may be scaled up again at any time by the OLM or whatever.