gcloud
CLI tool, or through the web UI—whichever you find more convenient.Note: Ifgcloud
throws unexpected permission-related errors during this process, make sure you've been authenticated viagcloud auth login
.
kubectl config get-contexts
, the table shown should include a context with a NAME
and CLUSTER
equal to the cluster name you chose previously.kubectl get ns
to verify that you're able to connect to your cluster.garden.yml
:garden --env=remote plugins kubernetes cluster-init
, then garden dev --env=remote
. Now you should be good to go.kubectl describe service --namespace=garden-system garden-nginx-ingress-nginx-controller | grep 'LoadBalancer Ingress'
and make note of returned IP address.A
record pointing your-project.your-domain.com at that IP). We recommend setting up a wildcard record as well (e.g *.your-project.your-domain.com).Note: Your IAM role may need to have permissions to createclusterRoles
andclusterRoleBindings
.
kubectl config get-contexts
, the table shown should include a context with a NAME
and CLUSTER
equal to the cluster name you chose previously.kubectl get ns
to verify that you're able to connect to your Azure cluster.persistenvolumeclaim
modules, consult the storage classes documentation provided by AWS.kubectl
context and set it as the active context. Note the name of the context and create an environment for the cluster in your project garden.yml
:kops validate cluster
to check its status), initialize it with