Releases: ory/k8s
Releases · ory/k8s
v0.19.1
Major Ingress update
Release v0.19.0 marks addressing a major breaking change.
With #305 merged we officially stop supporting older version of kubernetes leaving only support for 1.18+ features.
We have created a guide for all those, still on the older versions, that should help in the transitioning process:
From 0.19.0
Since this version we support only kubernetes >= v1.18 for the ingress definition.
If you enabled ingresses you need to migrate values from:
ingress:
read:
hosts:
- host: chart-example.local
paths: ["/read"]
write:
hosts:
- host: chart-example.local
paths: ["/write"]to
ingress:
read:
className: ""
hosts:
- host: chart-example.local
paths:
- path: /read
pathType: Prefix
write:
className: ""
hosts:
- host: chart-example.local
paths:
- path: /write
pathType: Prefixwhere changes are on:
- introduce the
classNameto specify the ingress class documentation that need to be used - change
pathsdefinition from an array of strings to an array of objects, where each object include thepathand thepathType(see path matching documentation)
v0.18.0
v0.17.0
v0.16.0
feat: add watcher pilot (#293) This PR introduces a sidecar container to each deployment using the DSN mechanism. It allows setting a watcher for a mounted file, and restarting the deployment upon changes in the file. This uses inotify-tools, which report upon file changes. In this case we are operating with k8s volumes, which are mounted in some location and symlinked into the desired location. Change to the original file (so unmount and remount) causes the symlink to be deleted and recreated. In some cases this can break the program (f.e if the mounted file is a secret/certificate used by DSN) requiring a restart.