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
where cluster-spec.yaml represents the cluster spec file for a workload cluster and --kubeconfig points to the kubeconfig file of a management cluster.
Why is this needed:
The text was updated successfully, but these errors were encountered:
mdsgabriel
changed the title
Create Workload clusters using existing Management clusters
Create Workload clusters using an existing Management cluster
Oct 5, 2021
This will introduce a new optional flag (--kubeconfig) that will be used
when creating workload clusters.
Users will run the following command:
eksctl anyhwere create cluster -f workload-cluster-spec.yaml
--kuneconfig management.kubeconfig
Where "management.kubeconfig" is the kubeconfig file of an existing
management cluster.
The command above will create a workload cluster.
Closesaws#386
* Allow users to create wokload clusters
This will introduce a new optional flag (--kubeconfig) that will be used
when creating workload clusters.
Users will run the following command:
eksctl anyhwere create cluster -f workload-cluster-spec.yaml
--kuneconfig management.kubeconfig
Where "management.kubeconfig" is the kubeconfig file of an existing
management cluster.
The command above will create a workload cluster.
Closesaws#386
* Use cluster name when listing machines
The GetMachines() method was previously listing all Machine CRs in the
cluster. With the introduction of Workload clusters it is necessary to
filter machines using the cluster name
* Fix logic
What would you like to be added:
Allow users to create workload clusters using an existing management cluster
Users will run a command similar to
where cluster-spec.yaml represents the cluster spec file for a workload cluster and --kubeconfig points to the kubeconfig file of a management cluster.
Why is this needed:
The text was updated successfully, but these errors were encountered: