Add Kubernetes Cluster Cloud Provider
When you create a Kubernetes cluster, you specify its authentication method. In Harness, you use this method to connect to the cluster using a Kubernetes Cluster Cloud Provider.
For more information, see Authenticating from Kubernetes.
In this topic:
- Before You Begin
- Visual Summary
- Review: Using a Delegate Inside or Outside of the Target Cluster
- Review: Kubernetes Cluster Cloud Provider vs Platform Cloud Providers
- Review: Permissions for the Kubernetes Role
- Step 1: Add the Cloud Provider
- Step 2: Cluster Details
- Option 1: Inherit from selected Delegate
- Option 2: Enter manually
- Step 3: Skip Validation
- Step 4: Credential Validation
- Review: Permissions Required
- Option: AWS EKS Support
- Option: OpenShift Support
Before You Begin
- See Harness Key Concepts.
Visual Summary
Here's an overview of the settings required to add a Kubernetes Cluster as Cloud Provider.
Review: Using a Delegate Inside or Outside of the Target Cluster
Typically, you install the Harness Kubernetes Delegate inside your target cluster and then add a Kubernetes Cluster Cloud Provider that inherits its credentials from the Delegate.
You can also install the Kubernetes Delegate outside of the target cluster (anywhere in your environment).
In this case, the Kubernetes Cluster Cloud Provider will not inherit credentials from the Delegate, but use the target cluster master URL and some authentication method (Service Account Token, etc).