        │        │         │            │        ┃┃        │                   │                                      │        │ 🌀 kubernetes-cluster │               │        │         │            │        ┃

┃        │                   │                                      │        │ 🐳 docker-registry    │               │        │         │            │        ┃

┗━━━━━━━━┷━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━┷━━━━━━━━┷━━━━━━━━━┷━━━━━━━━━━━━┷━━━━━━━━┛

This checks the Kubernetes clusters that the AWS Service Connector has access to:

zenml service-connector verify aws-session-token --resource-type kubernetes-cluster

Example Command Output

Service connector 'aws-session-token' is correctly configured with valid credentials and has access to the following resources:

┏━━━━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━┓

┃     RESOURCE TYPE     │ RESOURCE NAMES   ┃

┠───────────────────────┼──────────────────┨

┃ 🌀 kubernetes-cluster │ zenhacks-cluster ┃

┗━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━┛

Running the login CLI command will configure the local kubectl CLI to access the Kubernetes cluster:

zenml service-connector login aws-session-token --resource-type kubernetes-cluster --resource-id zenhacks-cluster

Example Command Output

⠇ Attempting to configure local client using service connector 'aws-session-token'...

Cluster "arn:aws:eks:us-east-1:715803424590:cluster/zenhacks-cluster" set.

Context "arn:aws:eks:us-east-1:715803424590:cluster/zenhacks-cluster" modified.

Updated local kubeconfig with the cluster details. The current kubectl context was set to 'arn:aws:eks:us-east-1:715803424590:cluster/zenhacks-cluster'.

The 'aws-session-token' Kubernetes Service Connector connector was used to successfully configure the local Kubernetes cluster client/SDK.

The following can be used to check that the local kubectl CLI is correctly configured:

kubectl cluster-info

Example Command Output