Browse Source

Clarification of kubectl involvement in `deploy` command and potential error reason (#986)

darc-main-e5ea0866-8be1-4711-8688-8fd9b7dae18a
Oleg Karasik 6 years ago
committed by GitHub
parent
commit
3756e2a60e
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 3
      docs/tutorials/hello-tye/01_deploy.md

3
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:

Loading…
Cancel
Save