Max Bowsher

The Vault Helm chart already sets up an ingress. And it works for accessing the UI as well as the API.

Delete the entire `ingress` block and the entire `ui` block. That works for me.

Oh, whoops, I'd forgotten that I simply defined a simple ingress outside Helm ``` apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: vault spec: rules: - host: x.y.z http: paths: - path:...

OK, I deleted my manually-created ingress, and added to the Helm values: ``` server: ingress: enabled: true hosts: - host: x.y.z ``` That results in Helm generating the identical ingress...

Change your values.yaml to ``` server: ha: enabled: true replicas: 3 config: | ui = true storage "consul" { path = "vault" address = "my-consul.mywebsite.com:8500" } ingress: enabled: true hosts:...

This appears to be a combination of factors coming together to produce undesired behaviour: 1) Root tokens are not saved by the UI, so you are immediately logged out if...

I just came across this too - ed25519 keys can't be used with the auth agent, which is a shame. Confirming still an issue with connectbot 1.9.8 in 2022

> Likely adding a new line will break existing deployments, where the absence of a newline is currently expected. Since the PEM format is inherently line-based, it is difficult for...

Ah, I see. I can't deny the possibility of such a parser existing somewhere. It would be a pretty sloppy implementation, but humans write bad code all the time. On...

I wonder if, as part of finalizing this journey, it might make sense to revisit whether to continue setting the `netcgo` build tag, as well? According to the big comment...