Helidon is a collection of Java libraries for writing microservices. Helidon provides an open source, lightweight, fast, reactive, cloud native framework for developing Java microservices. It is available as two frameworks:
- Helidon SE is a compact toolkit that embraces the latest Java SE features: reactive streams, asynchronous and functional programming, and fluent-style APIs.
- Helidon MP implements and supports Eclipse MicroProfile, a baseline platform definition that leverages Java EE and Jakarta EE technologies for microservices and delivers application portability across multiple runtimes.
Helidon is designed and built with container-first philosophy.
- Small footprint, low memory usage and faster startup times.
- All 3rd party dependencies are stored separately to enable Docker layering.
- Provides readiness, liveness and customizable health information for container schedulers like Kubernetes.
Containerized Helidon applications are generally deployed as Deployment in Kubernetes.
Helidon applications are first class citizens in Verrazzano with specialized Helidon workload support, for example,
VerrazzanoHelidonWorkload. VerrazzanoHelidonWorkload is supported as part of
verrazzano-application-operator in the
Verrazzano installation and no additional operator setup or installation is required. VerrazzanoHelidonWorkload also supports all
the Traits and Scopes defined by Verrazzano along with core ones defined by the OAM specification.
VerrazzanoHelidonWorkload is modeled after ContainerizedWorkload, for example, it is used for long-running workloads in containers. However, VerrazzanoHelidonWorkload closely resembles and directly refers to Kubernetes Deployment schema. This enables an easy lift and shift of existing containerized Helidon applications.
The complete VerrazzanoHelidonWorkload API definition and description is available at VerrazzanoHelidonWorkload.
Verrazzano Helidon application development
With Verrazzano, you manage the life cycle of applications using Component and ApplicationConfiguration resources. A Verrazzano application can contain any number of VerrazzanoHelidonWorkload components, where each workload is a standalone containerized Helidon application, independent of any other in the application.
In the following example, everything under the
spec: section is the custom resource YAML file for the containerized Helidon application,
as defined by the VerrazzanoHelidonWorkload custom resource. Including this Component reference in your ApplicationConfiguration
will result in a new containerized Helidon application being provisioned.
apiVersion: core.oam.dev/v1alpha2 kind: Component metadata: name: hello-helidon-component namespace: hello-helidon spec: workload: apiVersion: oam.verrazzano.io/v1alpha1 kind: VerrazzanoHelidonWorkload metadata: name: hello-helidon-workload labels: app: hello-helidon spec: deploymentTemplate: metadata: name: hello-helidon-deployment podSpec: containers: - name: hello-helidon-container ... ...
The Steps to Deploy using OAM provides end-to-end instructions for developing and deploying the Verrazzano Helidon application.
For more Verrazzano Helidon application examples, see Examples.
Customizing Helidon Workload service
By default, deploying a Helidon Workload will create a service to access the Helidon pod. That service
can be customized by added a
serviceTemplate to the
VerrazzanoHelidonWorkload spec. This supports customizing the
serviceSpec sections to do things, like add labels and annotations, customize the service ports,
modify the pod selector, and such. It is not necessary to provide complete
serviceSpec sections. Just add the fields you
would like to customize and Verrazzano will create the rest of the fields, based the information
provided in the
deploymentTemplate. When customizing service ports, refer to Protocol Selection
in the Istio documentation.
apiVersion: core.oam.dev/v1alpha2 kind: Component metadata: name: hello-helidon-component namespace: hello-helidon spec: workload: apiVersion: oam.verrazzano.io/v1alpha1 kind: VerrazzanoHelidonWorkload metadata: name: hello-helidon-workload labels: app: hello-helidon spec: deploymentTemplate: metadata: name: hello-helidon-deployment podSpec: containers: - name: hello-helidon-container ... ... serviceTemplate: metadata: name: hello-helidon-service serviceSpec: ports: - name: http-hello-helidon ... ...
When you apply the previous Component YAML file, Kubernetes will create a
component.oam.verrazzano.io resource, but
the containerized Helidon application will not be created until you create the ApplicationConfiguration resource,
which references the VerrazzanoHelidonWorkload component. When the application is created, Verrazzano creates a
Deployment and Service resource for each containerized Helidon application.
Typically, you would modify the Deployment and Service resource to make changes or to do lifecycle operations,
like scale in and scale out. However, in the Verrazzano environment, the containerized Helidon application resource is owned
verrazzano-application-operator and will be reconciled to match the component workload resource. Therefore,
you need to manage the application configuration by modifying the VerrazzanoHelidonWorkload or ApplicationConfiguration resource,
kubectl edit or applying a new YAML file. Verrazzano will notice the Component resource change and will update
the Deployment and Service resource as needed.
You can add a new VerrazzanoHelidonWorkload to a running application, or remove an existing workload, by modifying the ApplicationConfiguration resource and adding or removing the VerrazzanoHelidonWorkload component.
The recommended way to scale containerized Helidon application replicas is to specify a ManualScalerTrait
with the VerrazzanoHelidonWorkload in the ApplicationConfiguration. The following example
configuration shows the
replicaCount field that specifies the number of replicas for the application.
... spec: components: - componentName: hello-helidon-component traits: - trait: apiVersion: core.oam.dev/v1alpha2 kind: ManualScalerTrait spec: replicaCount: 2 ...
Verrazzano will modify the Deployment resource
replicas field and the containerized Helidon application replicas will
be scaled accordingly.
NOTEMake sure the
replicasdefined on the VerrazzanoHelidonWorkload component and that the
replicaCountdefined on the ManualScalerTrait for that component match, or else the DeploymentController in Kubernetes and OAM runtime in
verrazzano-application-operatorwill compete to create a different number of Pods for same containerized Helidon application. To avoid confusion, we recommend that you specify
replicaCountdefined on the ManualScalerTrait and leave
replicasundefined on VerrazzanoHelidonWorkload (as it is optional).
When a containerized Helidon application is provisioned on Verrazzano, Verrazzano will configure the default logging and send logs to OpenSearch. You can view the logs using the OpenSearch Dashboards.
The logs are placed in a per-namespace OpenSearch data stream named
verrazzano-application-hello-helidon. All logs from containerized Helidon application pods in the same namespace will
go into the same data stream, even for different applications. This is standard behavior and there is no way to disable or change it.
Verrazzano uses Prometheus to scrape metrics from containerized Helidon application pods. Like logging, metrics scraping is also enabled during provisioning. You can view metrics using the Grafana console.
Using the MetricsTrait custom resource, you can customize configuration information needed to enable metrics for an application component.
Using the IngressTrait custom resource, you can configure traffic routing to a containerized Helidon application for an application component.
Whenever you have a problem with your Verrazzano Helidon application, there are some basic techniques you can use to troubleshoot. Troubleshooting shows you some simple things to try, as well as how to solve common problems you may encounter.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.