You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
According to the documentation, the first step in integrating the downstream Rancher cluster with the Harvester cloud provider is to create a service account in the Harvester cluster and "associate" kubeconfig with it. This kubeconfig has to be passed as argument to machine_selector_config block of a rancher2_cluster_v2 resource.
Service account must be created manually using an API call (curl). Would be nice to have a terraform resource that implements this feature
Describe the solution you'd like
Ideally, it would be great to have a resource that takes k8s cluster namespace and service account as parameters and returns kubeconfig associated with the service account.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
According to the documentation, the first step in integrating the downstream Rancher cluster with the Harvester cloud provider is to create a service account in the Harvester cluster and "associate" kubeconfig with it. This kubeconfig has to be passed as argument to machine_selector_config block of a rancher2_cluster_v2 resource.
Service account must be created manually using an API call (curl). Would be nice to have a terraform resource that implements this feature
Describe the solution you'd like
Ideally, it would be great to have a resource that takes k8s cluster namespace and service account as parameters and returns kubeconfig associated with the service account.
The text was updated successfully, but these errors were encountered: