Preflight checklist
Ory Network Project
No response
Describe the bug
There were new fields added to the Maester OAuth2Client CRD in v0.0.40 but were never brought into the charts repo when the version was updated.
CRD in version 0.60.1 of k8s (includes v0.0.40 of Maester):
https://github.com/ory/k8s/blob/0ba60c3ea001f0772399d0cbf099ba1aaddf8b9f/helm/charts/hydra-maester/crds/crd-oauth2clients.yaml
CRD in version 0.0.40 of Maester:
https://github.com/ory/hydra-maester/blob/944b2ccaa0473dc2cfd62c5d8e10c76371237fd4/config/crd/bases/hydra.ory.sh_oauth2clients.yaml
Values such as skipLogoutConsent missing in the k8s repo version.
Seems like some part of the release process for these charts wasn't completed when renovate updated the charts:
#811
Reproducing the bug
Templating the latest charts for Hydra/Maester don't include CRD fields that are in the latest version of Hydra Maester
Relevant log output
Relevant configuration
Version
0.60.1
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response
Preflight checklist
Ory Network Project
No response
Describe the bug
There were new fields added to the Maester OAuth2Client CRD in v0.0.40 but were never brought into the charts repo when the version was updated.
CRD in version 0.60.1 of k8s (includes v0.0.40 of Maester):
https://github.com/ory/k8s/blob/0ba60c3ea001f0772399d0cbf099ba1aaddf8b9f/helm/charts/hydra-maester/crds/crd-oauth2clients.yaml
CRD in version 0.0.40 of Maester:
https://github.com/ory/hydra-maester/blob/944b2ccaa0473dc2cfd62c5d8e10c76371237fd4/config/crd/bases/hydra.ory.sh_oauth2clients.yaml
Values such as
skipLogoutConsentmissing in the k8s repo version.Seems like some part of the release process for these charts wasn't completed when renovate updated the charts:
#811
Reproducing the bug
Templating the latest charts for Hydra/Maester don't include CRD fields that are in the latest version of Hydra Maester
Relevant log output
Relevant configuration
Version
0.60.1
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response