Jakub Błaszczyk

Hi there! I think you should be able to use our Env variables to workaround this. Basically, each config option can be passed as an env to ory apps, so...

@nickperkins did the mentioned solution work for you?

Do you foresee any other major changes? Asking because we can either `if` the charts depending on the version of hydra, or just implement the breaking changes and point that...

Hi there. This piece of documentation is actually in the root of the documents: http://k8s.ory.sh/helm/ 😉

Closing due to https://github.com/ory/k8s/pull/504 implementing similar feature set :)

Hello there, I think I understand what you are getting at, but in the context of k8s there already are community approved standards for handling certificates. One of them would...

Let me rephrase that :) ``` SERVE_TLS_KEY_PATH=/path/to/key.pem SERVE_TLS_CERT_PATH=/path/to/cert.crt ``` You would set those envs (or configs in the config file) to a path on the container filesystem, and then mount...

The watcher is a dedicated deployment that watches over mounted files, it does not know the envs used by hydra, but mounts all volumes that hydra would. Please take a...

In Hydra the option is named `deployments.labels`, but it provides the same function. We could and probably should unify the naming convention across the charts 😞

Hi there! The warning are as you noticed, mostly caused by the use of `tpl` functions which expect strings in places you would expect and object or array. I agree,...