From 3756e2a60e1e64492ac8e9749ce5a0cdc1744878 Mon Sep 17 00:00:00 2001 From: Oleg Karasik Date: Fri, 26 Mar 2021 19:19:10 +0300 Subject: [PATCH] Clarification of kubectl involvement in `deploy` command and potential error reason (#986) --- docs/tutorials/hello-tye/01_deploy.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/tutorials/hello-tye/01_deploy.md b/docs/tutorials/hello-tye/01_deploy.md index d44d9488..2ac6440b 100644 --- a/docs/tutorials/hello-tye/01_deploy.md +++ b/docs/tutorials/hello-tye/01_deploy.md @@ -30,11 +30,12 @@ Now that we have our application running locally, let's deploy the application. ```text tye deploy --interactive ``` - > Enter the Container Registry (ex: 'example.azurecr.io' for Azure or 'example' for dockerhub): You will be prompted to enter your container registry. This is needed to tag images, and to push them to a location accessible by kubernetes. + > :bulb: Under the hood `tye` uses `kubectl` and to execute deployments. In cases if you don't have `kubectl` installed or it's current context is invalid `tye deploy` will fail with the following error: "Drats! 'deploy' failed: Cannot apply manifests because kubectl is not installed." + If you are using dockerhub, the registry name will your dockerhub username. If you are a standalone container registry (for instance from your cloud provider), the registry name will look like a hostname, eg: `example.azurecr.io`. `tye deploy` does many different things to deploy an application to Kubernetes. It will: