Skip to content

Instantly share code, notes, and snippets.

@janeczku

janeczku/rancher-vs-service-account-tokens.md

Last active August 26, 2020 14:00
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save janeczku/ce973255a1c648c3bee10f4f85560b2e to your computer and use it in GitHub Desktop.
Save janeczku/ce973255a1c648c3bee10f4f85560b2e to your computer and use it in GitHub Desktop.
Download ZIP
The different scopes of Rancher API tokens vs. Kubernetes Service Account tokens
Raw
rancher-vs-service-account-tokens.md

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 -
Manage in Rancher GUI x -
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment