Okteto Cloud gives instant access to secure Kubernetes namespaces to enable developers to code, build, and run Kubernetes applications entirely in the cloud.
This tutorial will show you how to develop and debug a Java sample application running in Okteto Cloud.
- Install the Okteto CLI >= 1.9.0. Follow this guide if you haven't done it yet.
- Configure access to your Okteto Cloud Namespace using the Okteto CLI or using the Okteto Cloud UI.
Step 1: Deploy the Java Sample App
Get a local version of the Java Sample App by executing the following commands:
k8s.yml file contains the Kubernetes manifests of the Java Sample App.
Deploy a dev version of the application by executing:
Log into Okteto Cloud and click on the URL of the application:
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: Create your okteto manifest
To start developing on the Java Sample App you first need to create an okteto manifest. With the Java Sample App deployed, run the following command to create your okteto manifest:
okteto init command will scan the available deployments in your Kubernetes namespace and ask you to pick one.
hello-world deployment. It's the one we deployed on the previous step.
okteto init command creates the following
This file defines how to activate a development container for the Java Sample App:
name: the name of the Kubernetes deployment you want to put on development mode
image: the image used by the development container. More information on development images here
command: the start command of the development container
volumes: a list of paths in your development container to be mounted as persistent volumes. This is useful to persist the maven/gradle caches.
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
okteto init command creates a
.stignore file to indicate which files shouldn't be synchronized to your development container.
This is useful to avoid synchronizing binaries, build artifacts, or git metadata.
Step 3: Activate your development container
With the Java Sample Application deployed, run the following command:
Working in your development container is the same as working on your local machine. Start the application by running the following command:
The first time you run the application, Maven/Gradle will compile your application. Wait for this process to finish.
Go back to the browser and reload the page to test that your application is running.
Step 4: Develop directly on Okteto Cloud
src/main/java/com/okteto/helloworld/RestHelloWorld.java in your favorite local IDE and modify the response message on line 11 to be Hello world from Okteto!. Save your changes.
Your IDE will auto compile only the necessary
*.class files which will be synchronized by Okteto to your application in Okteto Cloud. Take a look at the development container shell and notice how the changes are detected by Spring Boot and automatically hot reloaded.
spring-boot-devtoolsdependency to automatically restart your Java application whenever a file is changed.
Go back to the browser and reload the page. Your code changes were instantly applied. No commit, build, or push required 😎!
Step 5: 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 Eclipse, one of the most popular IDEs for Java development.
Add the following JVM arguments in the Gradle/Maven configuration files to enable remote debugging in your Java application:
Open the Debug configuration dialog, add a new Remote Java Application debug configuration, and point it to
Click the Debug button to start a debugging session. Add a breakpoint on
src/main/java/es/okteto/helloworld/RestHelloWorld.java, line 11. 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...
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? 😉
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 in 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!
Ready to develop your application on Okteto Cloud? Read our step by step tutorial on how to configure an Okteto Pipeline to deploy realistic environments for your application in just one click.