Skip to main content
Version: 1.14

Install and Configure

Okteto's Development Environments enable you to automatically deploy your application to a cloud development environment and see all of your code changes the moment you hit 'save' locally on your machine.

These Development Environments work using a combination of the Okteto platform, which is used to deploy your application, and Okteto CLI, which is used to launch the Development Environment. This guide will teach how to get started with remote Development Environments.

Installing Okteto CLI

Install the Okteto CLI following these steps:

MacOS / Linux

$ curl -sSfL | sh

If you need a specific version you can set the OKTETO_VERSION environment variable:

$ curl -sSfL | OKTETO_VERSION=2.3.3 sh

You can also install it via brew by running:

$ brew install okteto


Download and add it to your $PATH.

You can also install it via scoop by running:

$ scoop install okteto

For updating okteto with scoop, you might need to scoop unhold okteto & scoop update okteto or scoop uninstall okteto & scoop install okteto


Alternatively, you can directly download the binary from GitHub or build it directly from the source code.

Configuring Okteto CLI with Okteto

You can launch a remote Development Environment on the Okteto platform or any Kubernetes cluster with the Okteto CLI. For this guide, we'll be using Okteto's SaaS platform.

The first thing you need to do is configure Okteto CLI to use Okteto's platform. To do this, run the command below:

$ okteto context use

You can confirm that your CLI is configured by running the command below:

$ okteto context list
Name                          Namespace       Builder                                 Registry * cindylopez tcp://

Okteto offers a fully self-hosted version of our product, which may be more suitable for your organization.

Define Your Okteto Manifest

For Okteto CLI to know how to launch your Development Environment, it needs an Okteto manifest. This manifest is used to configure for your Development Environment. Okteto CLI will analyze any existing manifests (Helm, Kubernetes, etc.) in your source code directory and help you write an Okteto manifest for your application.

The Okteto manifest is required in all cases except when a Docker compose file exists and is configured for your application.

If you don't have an Okteto manifest for your application, you can run okteto init to generate one. You can then edit the manifest based on your application needs. Learn more about the manifest here.

For this guide we already have the Okteto manifest configured for our application so this step won't be needed.

Next Steps

In this section we installed Okteto CLI on our machine, configured it to work with Okteto's platform, and provided context for the role the Okteto Manifest plays in deploying a Development Environment.

Next we're going to launch our Development Environment and fix a bug in a sample application.