Developing with Java (Spring Boot)
Step 0. Creating the initial source code (optional)
We will create the example source code by using some popular frameworks.
Before we begin, we will create a new directory and cd into it.
mkdir quickstart-demo && cd quickstart-demo
This is optional and you may use an existing project instead (make sure you cd into the project directory before running any odo commands) or a starter project from odo init
.
For Java, we will use the Spring Initializr to generate the example source code:
- Navigate to start.spring.io.
- Select Maven under Project.
- Click on "Add" under "Dependencies".
- Select "Spring Web".
- Click "Generate" to generate and download the source code.
Finally, extract the downloaded source code archive in the 'quickstart-demo' directory.
Your source code has now been generated and created in the directory.
Step 1. Preparing the target platform
- Podman
- Kubernetes
- OpenShift
Before starting on Podman, you should have Podman installed and configured properly on your machine. See Podman installation instructions for further details.
You also need odo
3.8.0 or later.
To make sure that odo
has the appropriate version and detects your local Podman,
run the command below and check that it reports the Podman Client version.
odo version
Sample Output
$ odo version
⚠ unable to fetch the cluster server version
odo v3.13.0 (6c1c8b2a1)
Podman Client: 4.6.0
Before starting, you should make sure that odo is connected to your cluster and that you have created a new namespace.
Creating a new namespace
If you are using Kubernetes, you can create a new namespace with the odo create namespace
command.
odo create namespace odo-dev
Sample Output
$ odo create namespace odo-dev
✓ Creating the namespace "odo-dev" [1s]
✓ Namespace "odo-dev" is ready for use
✓ New namespace created and now using namespace: odo-dev
Before starting, you should make sure that odo is connected to your cluster and that you have created a new project.
Login to OpenShift Cluster
The easiest way to connect odo
to an OpenShift cluster is use copy "Copy login command" function in OpenShift Web Console.
- Login to OpenShift Web Console.
- At the top right corner click on your username and then on "Copy login command".
- You will be prompted to enter your login credentials again.
- After login, open "Display Token" link.
- Copy whole
oc login --token ...
command and paste it into the terminal, before executing the command replaceoc
withodo
.
Create a new project
If you are using OpenShift, you can create a new namespace with the odo create project
command.
odo create project odo-dev
Sample Output
$ odo create project odo-dev
✓ Creating the project "odo-dev" [1s]
✓ Project "odo-dev" is ready for use
✓ New project created and now using project: odo-dev
Step 2. Initializing your application (odo init
)
Now we'll initialize your application by creating a devfile.yaml
to be deployed.
odo
handles this automatically with the odo init
command by autodetecting your source code and downloading the appropriate Devfile.
Note: If you skipped Step 0, select a "starter project" when running odo init
.
Let's run odo init
and select Java (Spring Boot):
odo init
Sample Output
$ odo init
__
/ \__ Initializing a new component
\__/ \ Files: Source code detected, a Devfile will be determined based upon source code autodetection
/ \__/ odo version: v3.16.1
\__/
Interactive mode enabled, please answer the following questions:
✓ Determining a Devfile for the current directory [1s]
Based on the files in the current directory odo detected
Supported architectures: all
Language: Java
Project type: springboot
The devfile "java-springboot:1.3.0" from the registry "DefaultDevfileRegistry" will be downloaded.
? Is this correct? Yes
✓ Downloading devfile "java-springboot:1.3.0" from registry "DefaultDevfileRegistry" [3s]
↪ Container Configuration "tools":
OPEN PORTS:
- 8080
- 5858
ENVIRONMENT VARIABLES:
- DEBUG_PORT = 5858
? Select container for which you want to change configuration? NONE - configuration is correct
? Enter component name: my-java-app
You can automate this command by executing:
odo init --name my-java-app --devfile java-springboot --devfile-registry DefaultDevfileRegistry --devfile-version 1.3.0
Your new component 'my-java-app' is ready in the current directory.
To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
Changes will be directly reflected on the cluster.
If you skipped Step 0 and selected "starter project", your output will be slightly different.
Step 3. Developing your application continuously (odo dev
)
Now that we've generated our code as well as our Devfile, let's start on development.
odo
uses inner loop development and allows you to code,
build, run and test the application in a continuous workflow.
Once you run odo dev
, you can freely edit code in your favourite IDE and watch as odo
rebuilds and redeploys it.
Let's run odo dev
to start development on your Java (Spring Boot) application:
- Podman
- Kubernetes
- OpenShift
odo dev --platform podman
Sample Output
$ odo dev --platform podman
__
/ \__ Developing using the "my-java-app" Devfile
\__/ \ Platform: podman
/ \__/ odo version: v3.16.1
\__/
↪ Running on podman in Dev mode
✓ Deploying pod [6s]
✓ Syncing files into the container [234ms]
✓ Building your application in container (command: build) [43s]
• Executing the application (command: run) ...
✓ Waiting for the application to be ready [1s]
- Forwarding from 127.0.0.1:20001 -> 8080
↪ Dev mode
Status:
Watching for changes in the current directory /home/user/quickstart-demo
Keyboard Commands:
[Ctrl+c] - Exit and delete resources from podman
[p] - Manually apply local changes to the application on podman
odo dev
Sample Output
$ odo dev
__
/ \__ Developing using the "my-java-app" Devfile
\__/ \ Namespace: odo-dev
/ \__/ odo version: v3.16.1
\__/
↪ Running on the cluster in Dev mode
• Waiting for Kubernetes resources ...
✓ Added storage m2 to component
⚠ Pod is Pending
✓ Pod is Running
✓ Syncing files into the container [167ms]
✓ Building your application in container (command: build) [3m]
• Executing the application (command: run) ...
✓ Waiting for the application to be ready [1s]
- Forwarding from 127.0.0.1:20001 -> 8080
↪ Dev mode
Status:
Watching for changes in the current directory /home/user/quickstart-demo
Keyboard Commands:
[Ctrl+c] - Exit and delete resources from the cluster
[p] - Manually apply local changes to the application on the cluster
odo dev
Sample Output
$ odo dev
__
/ \__ Developing using the "my-java-app" Devfile
\__/ \ Namespace: odo-dev
/ \__/ odo version: v3.16.1
\__/
↪ Running on the cluster in Dev mode
• Waiting for Kubernetes resources ...
✓ Added storage m2 to component
⚠ Pod is Pending
✓ Pod is Running
✓ Syncing files into the container [167ms]
✓ Building your application in container (command: build) [3m]
• Executing the application (command: run) ...
✓ Waiting for the application to be ready [1s]
- Forwarding from 127.0.0.1:20001 -> 8080
↪ Dev mode
Status:
Watching for changes in the current directory /home/user/quickstart-demo
Keyboard Commands:
[Ctrl+c] - Exit and delete resources from the cluster
[p] - Manually apply local changes to the application on the cluster
Then wait a few seconds until odo dev
displays Forwarding from 127.0.0.1:...
in its output,
meaning that odo
has successfully set up port forwarding to reach the application running in the container.
You can now access the application via the local port displayed by odo dev
(127.0.0.1:20001 in the sample output above) and start your development loop.
odo
will watch for changes and push the code for real-time updates.
You can now follow the advanced guide to deploy the application to production.