ory/k8s v0.24.0 on GitHub

Breaking Changes

This release introduces a small, but breaking change to the following charts: hydra, keto, kratos:

Thanks to @DenisPalnitsky we have introduces the option to pick the type of automigration you want to have in your setup: job or initContainers. Each model comes with its own benefits and drawbacks:

Job is configured to always a singleton entity and runs once regardless of how many replicas of your deployment you have, but due to hooks it can not always work as expected in some managed scenarios
InitContainers are baked into the deployment, and do not require hooks, which simplifies the setup, but running multiple replicas would run the migration multiple times. Therefore it might be a good idea to scale down your deployments before an upgrade 😉

How to migrate

The migration procedure requires you to modify the values fro charts accordingly:

# v0.23
---
hydra:
  autoMigrate: true
---
# v0.24
hydra:
  automigration:
    enabled: true
    # job is the default value
    type: initContainer

What's Changed

chore: delete semantic.yml by @kevgo in #450
fix: ingress service targets by @Demonsthere in #454
fix: keto ingress wrong service name by @NV4RE in #458
feat: add extraEnvs support to example-idp by @Demonsthere in #461
feat: add horizontal pod autoscaler to oathkeeper helm chart by @PeteMac88 in #459
feat: allow setting auto migration as job or initcontainer in kratos by @DenisPalnitsky in #451
feat: expand automigration for all charts by @Demonsthere in #466

New Contributors

@kevgo made their first contribution in #450
@NV4RE made their first contribution in #458
@PeteMac88 made their first contribution in #459
@DenisPalnitsky made their first contribution in #451

Full Changelog: v0.23.3...v0.24.0