6 ms·
The biggest difference is that Teleport is a full MITM for all apiserver traffic, leveraging the cluster-local certificate authority for short-lived creds (simi
by aberoham 8y ago
The biggest difference is that Teleport is a full MITM for all apiserver traffic, leveraging the cluster-local certificate authority for short-lived creds (similar to how K8s internal bits such as the kubelet speaks TLS to the apiserver). Notably this also works with completely air-gapped clusters or end-users, or clusters where you want access to apiserver to be via egress (hidden bastion) only.
K8s authentication methods that go inline with the apiserver, such as oidc or dex, achieve the same goals but are a bit of a different design flavor and arguably less clean from a threat or failure model perspective.
- madjam002 8y agoHow is OIDC less clean from a threat/failure model perspective? If your organisation has implemented an OIDC IdP, you can have the API server behind a Bastion like you suggest, and accessible through an authenticating reverse proxy (Beyondcorp style) WAF. You can even have token bound access/ID tokens which are backed by hardware TPMs if you're REALLY paranoid (upcoming spec). Plus because it's an open standard which K8s heavily embraces, you get rich group/user claims mapping in K8s allowing for logging and auditing.