Adam Bozanich
Adam Bozanich
Thanks for this! Please update the top-level `README.md` as well. Note that we have tty access now - ssh shouldn't be needed.
Hi @wlouie1! I'm so sorry for the delay. I'd love to get this in, but would you mind updating the auditor key like is done in #185?
Thanks for the contribution, @Rashmi-278 ! Can you add an entry to the top-level readme?
@evan2645 we use it for for cross-cluster communications. there might be a couple of different postgres instances hosted on cluster A that services in cluster B need to talk to,...
@evan2645 : yeah, haproxy sits in front of a kube cluster and does the SNI vhosting ( SNI `pg1.cluster.com` -> kube service `postgres.ns1.svc` ) . haproxy builds configuration from kube...
I'm so sorry @mnaser! I've added you as a collaborator, you're welcome to merge.
Can you just point them to `_run/kube`?
The provider daemon itself is unnoticeable, but we should probably define some minimum requirements for running a real provider+cluster. I've seen the question asked a lot.