consul: add k8s servers joining the au-syd1 VM datacenter #531
Reference in New Issue
Block a user
Delete Branch "benvin/consul-k8s-servers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Consul servers in k8s join the VM
au-syd1datacenter as extra raft voters, so they need routable per-pod addresses, VM-matching ACL tokens and a TLS cert valid for the consul service names.acl-tokens.json, mounted as a hot-reloaded-config-dirconsul-server-tlsCertificate (vault-issuer) for HTTPS on 8501server-acland refresh the READMEcert-manager.io/alt-namesis not read by cert-manager gateway-shim (SANs come only from listener hostnames);consul-tlswill not coverconsul.service.au-syd1.consulorconsul, so TLS on the LB :443 fails for those names → add a standaloneCertificatewith those dnsNames for the pods (or matching listener hostnames) and drop the annotation-hclend up in process argv (/proc/*/cmdline) and are frozen at pod start, so VSO refreshes never reach the agent → mountconsul-server-aclas a config file under-config-dir(or set VSOrolloutRestartTargets)tcpSocket: 8301passes before the pod has joined or sees a leader, soconsul-dnsroutes to an unjoined server → exec-probe/v1/status/leaderfor a non-empty leader (per-pod LBs already publish not-ready, so no announce loop)allowPrivilegeEscalation: falseandcapabilities.drop: [ALL]No findings.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.