upplied a custom value while creating the cluster.Run the following command.
aws eks update-kubeconfig --name <NAME> --region <REGION>

Get the name of the deployed cluster.

zenml stack recipe output gke-cluster-name\

Figure out the region that the cluster is deployed to. By default, the region is set to europe-west1, which you should use in the next step if you haven't supplied a custom value while creating the cluster.\

Figure out the project that the cluster is deployed to. You must have passed in a project ID while creating a GCP resource for the first time.\

Run the following command.
gcloud container clusters get-credentials <NAME> --region <REGION> --project <PROJECT_ID>

You may already have your kubectl client configured with your cluster. Check by running kubectl get nodes before proceeding.

Get the name of the deployed cluster.

zenml stack recipe output k3d-cluster-name\

Set the KUBECONFIG env variable to the kubeconfig file from the cluster.

export KUBECONFIG=$(k3d kubeconfig get <NAME>)\

You can now use the kubectl client to talk to the cluster.

Stack Recipe Deploy

The steps for the stack recipe case should be the same as the ones listed above. The only difference that you need to take into account is the name of the outputs that contain your cluster name and the default regions.

Each recipe might have its own values and here's how you can ascertain those values.

For the cluster name, go into the outputs.tf file in the root directory and search for the output that exposes the cluster name.

For the region, check out the variables.tf or the locals.tf file for the default value assigned to it.

PreviousTroubleshoot the deployed server

NextCustom secret stores

Last updated 10 months ago