-
-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Oathkeeper helm chart 0.41 causes 503 #1165
Comments
Hi there! Can you share/take a look at the logs of the container? We could see some more info there. The upgrade itself passed, but for tests we use a very simplistic set of configs so we could easily miss some corner case 😞 |
Hey :) I'd have to re-upgrade my running cluster to get the logs, but I didn't collect or post any because there was nothing related to the 503, even with log level on debug. If I get a chance I'll find a time appropriate to break my environment to get any log output. |
😅 Yeah, obviously it's better not to break you env, but a failing health check should be logged as an event on the deployment/pod object, did you maybe take a look at that? Asking because right now I can't really do more then try to reproduce that upgrade with a minimal config as close to yours as possible 😞 |
I've done a search through our monitoring history to see if I could get the kubernetes events around the time I attempted the upgrade, but with no luck. I'll see if I can reproduce and report back with the k8s events. |
i encounter the same error after updating to 0.41. It uses the same values.yaml as before the update.
|
Same error for 0.40.1. Update to 0.39.1 resolved into no error. |
Same error here. I tried using the 0.42.0 helm chart that uses |
If this is a bug in Oathkeeper itself and not the chart or upgrade process, then maybe we should move this to the oathkeeper repo, as this could be regressions in the code itself, similar to #1161 |
Finally figured out what this issue was. The new charts don't allow you to configure maester separately. This is because in order for the rules configmap to be mounted correctly, you need My fix was to remove my own dependency on the maester chart, and allow oathkeeper to configure the child chart. |
Preflight checklist
Ory Network Project
N/A
Describe the bug
Upgrading the Oathkeeper chart to 0.41.0 causes oathkeeper to restart after 503 health check. I've not changed anything in the chart, and I don't use the secret (so it's
secret.false
for me).Reproducing the bug
Upgrade to chart 0.41.0, with
secret.false
Relevant log output
No response
Relevant configuration
Version
0.41.0
On which operating system are you observing this issue?
None
In which environment are you deploying?
Kubernetes with Helm
Additional Context
No response
The text was updated successfully, but these errors were encountered: