
┃ server                │ https://35.175.95.223 ┃┠───────────────────────┼───────────────────────┨

┃ insecure              │ False                 ┃

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

┃ cluster_name          │ 35.175.95.223         ┃

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

┃ token                 │ [HIDDEN]              ┃

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

┃ certificate_authority │ [HIDDEN]              ┃

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

Credentials auto-discovered and lifted through the Kubernetes Service Connector might have a limited lifetime, especially if the target Kubernetes cluster is managed through a 3rd party authentication provider such a GCP or AWS. Using short-lived credentials with your Service Connectors could lead to loss of connectivity and other unexpected errors in your pipeline.

Local client provisioning

This Service Connector allows configuring the local Kubernetes client (i.e. kubectl) with credentials:

zenml service-connector login kube-auto

Example Command Output

⠦ Attempting to configure local client using service connector 'kube-auto'...

Cluster "35.185.95.223" set.

⠇ Attempting to configure local client using service connector 'kube-auto'...

⠏ Attempting to configure local client using service connector 'kube-auto'...

Updated local kubeconfig with the cluster details. The current kubectl context was set to '35.185.95.223'.

The 'kube-auto' Kubernetes Service Connector connector was used to successfully configure the local Kubernetes cluster client/SDK.

Stack Components use

The Kubernetes Service Connector can be used in Orchestrator and Model Deployer stack component flavors that rely on Kubernetes clusters to manage their workloads. This allows Kubernetes container workloads to be managed without the need to configure and maintain explicit Kubernetes kubectl configuration contexts and credentials in the target environment and in the Stack Component.

PreviousDocker Service Connector