Skip to main content
Version: 1.7

Getting Started on Okteto Cloud with Node.js

Okteto Cloud gives instant access to secure Kubernetes namespaces to enable developers to code, build, and run cloud-native applications entirely in the cloud.

This tutorial will show you how to develop and debug a Node.js sample application running in Okteto Cloud.


Step 1: Deploy the Node.js Sample App

Get a local version of the Node.js Sample App by executing the following commands:

$ git clone
$ cd node-getting-started

At the root of the directory, you'll find the okteto.yaml file. This describes how to build and deploy the Node Sample App.

context: .
- kubectl apply -f k8s.yml

Deploy your development environment by executing:

$ okteto deploy --build
 i  Using cindy @ as context
i Building image for service 'hello-world'
i Building the image '' in tcp://
[+] Building 5.9s (11/11) FINISHED
✓ Image '' successfully pushed
i Running kubectl apply -f k8s.yml
deployment.apps/hello-world created
service/hello-world created created
✓ Development environment 'node-getting-started' successfully deployed
i Run 'okteto up' to activate your development container

Log into Okteto Cloud and click on the URL of the application:

Okteto Cloud UI Node.js

Did you notice that you're accessing your application through an HTTPs endpoint? This is because Okteto Cloud will automatically create them for you when you deploy your application. Cool no 😎?

Step 2: Activate your development container

The dev section defines how to activate a development container for the Node Sample App:

command: bash
- .:/usr/src/app
- 9229:9229

The hello-world key matches the name of the hello world Deployment. The meaning of the rest of fields is:

  • command: the start command of the development container.
  • sync: the folders that will be synchronized between your local machine and the development container.
  • forward: a list of ports to forward from your development container to localhost in your machine. This is needed to configure the Node debugger.

Also, note that there is a .stignore file to indicate which files shouldn't be synchronized to your development container. This is useful to avoid synchronizing binaries, build artifacts, git metadata, or dependencies like the node_modules folder.

Next, execute the following command to activate your development container:

$ okteto up
 ✓  Persistent volume successfully attached
✓ Images successfully pulled
✓ Files synchronized
Namespace: cindy
Name: hello-world
Forward: 9229 -> 9229

Welcome to your development container. Happy coding!
cindy:hello-world app>

Working in your development container is the same as working on your local machine. Start the application in hot-reload mode by running the following command:

cindy:hello-world app> npm run start
> node-getting-started@1.0.0 start /usr/src/app
> nodemon index.js

[nodemon] 2.0.18
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node index.js`
Starting hello-world server...

Go back to the browser and reload the page to test that your application is running.

Step 3: Develop directly on Okteto Cloud

Open the index.js file in your favorite local IDE and modify the response message on line 5 to be Hello world from the cluster!. Save your changes.

res.send("Hello world from the cluster!");

Okteto will synchronize your changes to your development container. Take a look at the development container shell and notice how the changes are detected by nodemon and automatically hot reloaded.

[nodemon] restarting due to changes...
[nodemon] starting `node index.js`
Starting hello-world server...

Go back to the browser and reload the page. Your code changes were instantly applied. No commit, build, or push required 😎!

Step 4: Debug directly on Okteto Cloud

Okteto enables you to debug your applications directly from your favorite IDE. Let's take a look at how that works in VS Code, one of the most popular IDEs for Node development. If you haven't done it yet, install the Node.js extension available from Visual Studio marketplace.

Cancel the execution of nodemon index.js from the development container shell by pressing ctrl + c. Rerun your application in debug mode:

cindy:hello-world app> npm run debug
Debugger listening on ws://
For help, see:

Open the Debug extension and run the Connect to okteto debug configuration (or press the F5 shortcut):

"version": "0.2.0",
"configurations": [
"name": "Connect to okteto",
"type": "node",
"request": "attach",
"address": "localhost",
"port": 9229,
"localRoot": "${workspaceFolder}",
"remoteRoot": "/usr/src/app",
"skipFiles": ["<node_internals>/**"]

You should be replacing the value of remoteRoot with wherever your application code is.

Add a breakpoint on index.js, line 5. Go back to the browser and reload the page. The execution will halt at your breakpoint. You can then inspect the request, the available variables, etc...

breakpoint in Node.js

Your code is running in Okteto Cloud, but you can debug it from your local machine without any extra services or tools. Pretty cool no? 😉

Next steps

Congratulations, you just developed your first application in Okteto Cloud 🚀.

Okteto lets you develop your applications directly on Kubernetes. This way you can:

  • Eliminate integration issues by developing on a realistic environment
  • Test your application end to end as fast as you type code
  • No more CPU cycles wasted in your machine. Develop at the speed of the cloud!

Find more advanced samples with Okteto in this repository or join our community to ask questions and share your feedback.