Andreas Gruhler
Andreas Gruhler
@kartuhn not sure if your question is still worth answering, but it might help anyone finding that issue here. You basically enable TLS on the Vault API by setting some...
Thank you @piotrkochan for mentioning. I think adding that variable `haproxy_default_backend_name` to your frontend settings should fix that issue, see last commit in that PR here.
@janosdebugs thanks for the follow-up. Yes, seems this is still an issue in the said browser. I just did a quick check.
I just noticed that we could probably achieve the same configuration by using the `vault_custom_configuration` value. However, adding the feature flag for this opt out is more explicit.
Hi @cdown did you check if this is related to https://github.com/42wim/matterircd/issues/527? I also had similar issues which I could fix simply by providing the correct arguments for login
Looking at https://semver.org/#spec-item-5, we only need to care about the "breaking" change if we have `1.*`? Because probably nobody takes your word for it before `1.*` anyways (i.e., it's not...
I was asked to do so in https://github.com/adfinis/helm-charts/pull/1157 but I can also included it here, just let me know
> do we have any news here? follow-up in https://github.com/adfinis/helm-charts/pull/1268