Getting Started on Okteto Cloud with ASP.NET

Okteto Cloud gives you free access to secure Kubernetes namespaces, fully integrated with remote development capabilities. Develop your Kubernetes applications in Okteto Cloud and forget about slow and tedious local development forever.

This tutorial will show you how to create an account in Okteto Cloud and how to develop an ASP.NET sample application.

Prerequisites

Step 1: Deploy the ASP.NET Sample App

Get a local version of the ASP.NET Sample App by executing the following commands:

$ git clone https://github.com/okteto/aspnetcore-getting-started
$ cd aspnetcore-getting-started

The k8s.yml file contains the Kubernetes manifests of the ASP.NET Sample App. Deploy a dev version of the application by executing:

$ kubectl apply -f k8s.yml
deployment.apps "hello-world" created
service "hello-world" created

Open your browser and go to the URL of the application. You can get the URL by logging into Okteto Cloud and clicking on the application's endpoint:

Did you notice that you are 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: Start your remote development environment

We are going to use the dev version of the ASP.NET Sample App we just deployed as our remote development environment. To do that, run the following command:

$ okteto up
โœ“ Development environment activated
โœ“ Files synchronized
Namespace: cindy
Name: hello-world
Forward: 5000 -> 5000
2222 -> 22
watch : Polling file watcher is enabled
watch : Started
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://0.0.0.0:5000
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: /src

The okteto up command starts a Kubernetes development environment, which means:

  • The ASP.NET Core Sample App container is updated with the Docker image okteto/hello-world:aspnetcore-dev. This image is based of mcr.microsoft.com/dotnet/core/sdk:3, and is preconfigured with all the required dev tools to build, test, debug and run a dotnetcore-based application. Check the Dockerfile to see how it is generated.
  • A file synchronization service is created to keep your changes up-to-date between your local filesystem and your application pods.
  • Container port 5000 is forwarded to localhost.

All of this (and more) can be customized via the okteto.yml manifest file.

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

Step 3: Develop directly in Okteto Cloud

Open the file Controllers/HelloWorldController.cs in your favorite local IDE and modify the response message on line 25 to be Hello world from Okteto!. Save your changes.

[HttpGet]
public string Get()
{
return "Hello world from Okteto!";
}

Take a look at the remote shell and notice how the changes are detected by dotnet watch run and automatically built and reloaded.

info: Microsoft.Hosting.Lifetime[0]
Application is shutting down...
watch : Exited
watch : File changed: /src/Controllers/HelloWorldController.cs
watch : Started
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://0.0.0.0:5000
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: /src

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 in 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 aausing the VS dotnet debugger.

For this step, we are going to use the C# extension for VS Code. If you don't have it, you can install it here. You might need to restart your VS Code instance.

Open HelloWorldController.cs in VS Code, set a breakpoint on line 26 and press F5. VS Code will connect to your remote development environment via SSH and give you a list of processes you can attach to. Scroll through the list, and select the helloworld process, as shown below (you can also type helloworld in the search bar directly).

Once you select the process, VS Code will switch to debug view, launch the debugger and attach it to the process you just selected. You'll know it's finished when the status bar at the bottom turns orange.

Go back to the browser and reload the page. As soon as the service receives the request the execution will halt at your breakpoint and VS Code will jump to the front of the screen. You can then inspect the request, the available variables, etc.

Your code is executing in Okteto Cloud, but you can debug it from your local machine without any extra services or tools. Pretty cool no? ๐Ÿ˜‰

Step 5: Redeploy the ASP.NET Sample App

Once you are happy with your changes, exit your development environment with ctrl + c.

If you want to keep your changes running, execute the following command in your local shell:

$ okteto push
i Running your build in Okteto Cloud
[+] Building 16.0s (16/16)
...
โœ“ Source code pushed to the development environment 'hello-world'

okteto push automatically builds a new image tag using the Okteto Build Service, pushes it to the Okteto Registry and redeploys your application with the new image tag ๐Ÿ’ฅ!

Alternatively, you can also rollback the ASP.NET Sample App to its original state (the one before running okteto up) by executing:

$ okteto down
โœ“ Development environment deactivated

Next steps

Congratulations, you just developed your first Kubernetes application in Okteto Cloud ๐Ÿš€.

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

  • Reduce local setup and eliminate integration issues by developing the same way your application runs in production
  • Test your application as fast as you type code, without typing either docker or kubectl in your inner loop cycle
  • No more CPU cycles wasted in your machine. Hardware and network just limited by the power of the cloud

Okteto uses the okteto.yml file to determine the name of your development environment, the docker image to use and where to upload your code. Check the Okteto manifest docs to customize your development environments with your own dev tools, images, and dependencies to adapt Okteto to your own application.

Find more advanced samples with Okteto in this repository or join our #okteto channel in the Kubernetes community Slack to make questions or share your feedback.