This table helps understand the nuances of using Rancher API tokens vs. using Kubernetes Service Account tokens to authenticate external clients such as Helm or CD solution.
| Scope & Features \ Token Type | Rancher API Token | Service Account Token |
|---|---|---|
| Rancher CLI | x | - |
| K8s clients (e.g. Helm, ArgoCD) | x | x |
| Rancher Endpoint (auth proxy) | x | - |
| Authorized Cluster Endpoint | x | x |
| Single Cluster Token | x | x |
| Multi-Cluster Token | x | - |