While troubleshooting a problem for a customer, we observed the controller segfaulting and restarting. Above is the last lines of its log when this happened. It looks like it got an error back from the Kubernetes Master API because it tried to specify an invalid Service.
If so, getting an error from k8s should not cause a segfault.
There's probably a handler that sends the error off to Sentry or something.
Slack thread https://uffizzi-internal.slack.com/archives/CN8MKSAQ5/p1691529749424879
While troubleshooting a problem for a customer, we observed the controller segfaulting and restarting. Above is the last lines of its log when this happened. It looks like it got an error back from the Kubernetes Master API because it tried to specify an invalid
Service.If so, getting an error from k8s should not cause a segfault.
There's probably a handler that sends the error off to Sentry or something.