Continued: Hydra Maester CRD not updated (v0.0.40) in v0.60.1 of k8s

Open

#855 opened on Mar 3, 2026 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 48/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: helm, kubernetes
Domain: devops

Research direction

Inspect the Kubernetes charts for v0.60.1 and compare their bundled CRDs with the Hydra Maester CRD referenced in the issue and previous issue #838. Start by finding how chart releases are produced, then verify that the updated CRD is included in a new chart release and that the Hydra client can be created without the reported boolean error.

Written by the indexing model from the issue text.

Description

bug

Preflight checklist

I could not find a solution in the existing issues, docs, nor discussions.
I agree to follow this project's Code of Conduct.
I have read and am following this repository's Contribution Guidelines.
I have joined the Ory Community Slack.
I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe the bug

Previous issue https://github.com/ory/k8s/issues/838

Looks like the CRD was merged into the repository but is still not available in the charts at v0.60.1. I assume this is because there hasn't been a new version created.

Without this hydra/hydra-maester is basically unusable as skipLogoutConsent(here) defaults null by both the maester CRDs and Hydra itself causing the creation of new clients to fail as Hydra expects a bool. Current workaround is to manually update the client with the API which defeats the purpose of maester 😂

A new release of the charts would be greatly appreciated.

Reproducing the bug

See previous issue https://github.com/ory/k8s/issues/838

Relevant log output

Relevant configuration

Version

v0.60.1

On which operating system are you observing this issue?

None

In which environment are you deploying?