Awesome

kcc: kube-credential-cache

Fast access to Kubernetes! Especially effective with kubectl + EKS, about 3~4x faster!

# first time access
$ time kubectl version &>/dev/null
kubectl version &> /dev/null  0.42s user 0.10s system 59% cpu 0.868 total

# cache effective
$ time kubectl version &>/dev/null
kubectl version &> /dev/null  0.05s user 0.02s system 24% cpu 0.308 total

Architecture

details is here (includes sequence diagram)

Features

Work as caching proxy of ExecCredential object, when use credential plugins of Kubernetes. (e.g. kubectl)

• kcc-cache
  • Cache ExecCredential object
  • Concern Command, Args, Env as cache-key
  • Cache file encryption
  • kubeconfig automated maintenance
• kcc-injector
  • kubeconfig optimize (inject kcc-cache command automatically)
  • kubeconfig recovery (remove injected commands)

Effects

A one of notable effect is, when used aws eks update-kubeconfig to access EKS. about 500ms(about 3~4x) faster!

benchmark is here

Installation

# go install
go install github.com/ryodocx/kube-credential-cache/cmd/kcc-cache@latest
go install github.com/ryodocx/kube-credential-cache/cmd/kcc-injector@latest

# asdf-vm: https://asdf-vm.com
asdf plugin add kube-credential-cache

# aqua: https://aquaproj.github.io
aqua g -i ryodocx/kube-credential-cache

or download from releases

Usage(edit kubeconfig)

:running: install & just run kcc-injector -i ~/.kube/config

:ambulance: restore kubeconfig: kcc-injector -i -r <your kubeconfig>

if manually edit kubeconfig,

• set kcc-cache to command
• original command move to args
• :warning: Do not use the same pattern for command, args and env
  • :warning:U sing the same pattern presents the risk of mixing up credentials
  • :warning: env is ignored if not in KUBE_CREDENTIAL_CACHE_CACHEKEY_ENV_LIST
  • if use kcc-injector, generate unique env KUBE_CREDENTIAL_CACHE_USER from user's name

EKS (same effect as kcc-injector -i <your kubeconfig>)

kind: Config
apiVersion: v1
clusters: [...]
contexts: [...]
current-context: <your-current-context>
preferences: {}
users:
  - name: user-name
    user:
      exec:
        apiVersion: client.authentication.k8s.io/v1beta1
-       command: aws
+       command: kcc-cache
        args:
+         - aws
          - --region
          - <your-region>
          - eks
          - get-token
          - --cluster-name
          - <your-cluster>
        env:
          - name: AWS_PROFILE
            value: <your-profile>

EKS with aws-vault

kind: Config
apiVersion: v1
clusters: [...]
contexts: [...]
current-context: <your-current-context>
preferences: {}
users:
  - name: user-name
    user:
      exec:
        apiVersion: client.authentication.k8s.io/v1beta1
-       command: aws
+       command: kcc-cache
        args:
+         - aws-vault
+         - exec
+         - <your-profile>
+         - --
+         - aws
          - --region
          - <your-region>
          - eks
          - get-token
          - --cluster-name
          - <your-cluster>
-       env:
-         - name: AWS_PROFILE
-           value: <your-profile>

kubeconfig specification

• https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/
• https://pkg.go.dev/k8s.io/client-go/tools/clientcmd/api/v1#Config

Troubleshooting

error: You must be logged in to the server (the server has asked for the client to provide credentials) at kubectl

Incorrect credentials may be cached.
For example, occur when using the wrong pair of aws-vault context and kubecontext.
The root cause is aws command return invalid credential without error.
Try remove cache file! In macOS: rm ~/Library/Caches/kube-credential-cache/cache.json
※see below kcc-cache configuration for other environment

...Corruption detected, recreate cache file

Detected broken cachefile.
The cause is unknown. However, we ignore error by recreating the cache currently.

Configration

kcc-cache

kcc-injector

$ kcc-injector -h
Usage: kcc-injector [flags] <kubeconfig filepath>
  -c string
        injection command (default "kcc-cache")
  -i    edit file in-place
  -r    restore kubeconfig to original