-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
deploy image of oathkeeper-maester to arm64 #623
Comments
+1 |
I found out that the maester is no longer being activity maintained. I believe there is a workaround without maester. set {
name = "maester.enabled"
value = "false"
} |
@0xHexE awesome I will give that a go! |
The arm based images have been added in https://github.com/ory/oathkeeper-maester/releases/tag/v0.1.9 |
Just override the oathkeeper-maester container tag in your oathkeeper-maester:
image:
tag: v0.1.10-arm64 Currently the maester dose not provide a multi-platform image. So i think this issue can be closed here. |
Closing this together with #723 as the fix has been released :) |
Preflight checklist
Describe your problem
I can see on the ory documentation that oathkeeper works on arm64 images however the helm chart relies on the oathkeeper-maester controller which does not support arm64 right now.
with the current setup on an arm64 cluster (graviton3) I get the following error
Describe your ideal solution
All that needs to be done is deploy a version with the arm64 flag and it should be good to go.
Workarounds or alternatives
NA
Version
latest
Additional Context
No response
The text was updated successfully, but these errors were encountered: