dentified by the kubernetes-cluster Resource Type.The resource name is a user-friendly cluster name configured during registration.

Authentication Methods

Two authentication methods are supported:

username and password. This is not recommended for production purposes.

authentication token with or without client certificates.

For Kubernetes clusters that use neither username and password nor authentication tokens, such as local K3D clusters, the authentication token method can be used with an empty token.

This Service Connector does not support generating short-lived credentials from the credentials configured in the Service Connector. In effect, this means that the configured credentials will be distributed directly to clients and used to authenticate to the target Kubernetes API. It is recommended therefore to use API tokens accompanied by client certificates if possible.

Auto-configuration

The Kubernetes Service Connector allows fetching credentials from the local Kubernetes CLI (i.e. kubectl) during registration. The current Kubernetes kubectl configuration context is used for this purpose. The following is an example of lifting Kubernetes credentials granting access to a GKE cluster:

zenml service-connector register kube-auto --type kubernetes --auto-configure

Example Command Output

Successfully registered service connector `kube-auto` with access to the following resources:

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

┃     RESOURCE TYPE     │ RESOURCE NAMES ┃

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

┃ 🌀 kubernetes-cluster │ 35.185.95.223  ┃

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

zenml service-connector describe kube-auto

Example Command Output

Service connector 'kube-auto' of type 'kubernetes' with id '4315e8eb-fcbd-4938-a4d7-a9218ab372a1' is owned by user 'default' and is 'private'.

'kube-auto' kubernetes Service Connector Details

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

┃ PROPERTY         │ VALUE                                ┃