Villain Microservice
Create a ConfigMap object to store application configurations
Click on
icon located at top right corner of web console.
Copy this YAML snippet to the editor and click Create button.
YAML snippet:
apiVersion: v1 kind: ConfigMap metadata: labels: app: rest-villains application: villains-service system: quarkus-super-heroes name: rest-villains-config data: quarkus.hibernate-orm.database.generation: validate quarkus.hibernate-orm.sql-load-script: no-file quarkus.datasource.jdbc.url: jdbc:otel:postgresql://villains-db:5432/villains_database quarkus.opentelemetry.tracer.exporter.otlp.endpoint: http://otel-collector:4317 quarkus.http.access-log.enabled: 'false' quarkus.http.access-log.pattern: > %h %l %u %t "%r" %s %b "User-Agent: %{i,User-Agent}" "x-request-id: %{i,x-request-id}" "x-b3-traceid: %{i,x-b3-traceid}" " Referer: %{i,Referer}"
Create a ConfigMap object A rest-villains-config ConfigMap object should be created.
Create a ConfigMap object
Create a Secret object to store the secret configurations
Click on
icon located at top right corner of web console.
Copy this YAML snippet to the editor and click Create button.
YAML snippet:
apiVersion: v1 kind: Secret metadata: labels: app: rest-villains application: villains-service system: quarkus-super-heroes name: rest-villains-config-creds data: quarkus.datasource.username: c3VwZXJiYWQ= quarkus.datasource.password: c3VwZXJiYWQ= type: Opaque
Create a Secret object A rest-villains-config-creds Secret object should be created.
Create a Secret object
Deploy application using OpenShift Build - Source-to-Image (S2I)
Go to Topology menu, right click on view area then select Add to Project -> Import from Git menu.
Deploy application container Click Show advanced Git options link then enter following inputs. OpenShift Build (S2I) will check the project e.g. source code, framework and select builder image for build/compile application for you.
Git Repo URL:
https://gitlab.com/s.audomsak/developer-advocacy-2022
Context dir:
code/rest-villains
Application:
villains-service
Name:
rest-villains
Deploy application container Scroll down to the bottom of the page, select 8080 option for Target port, uncheck the Create a route checkbox, and then click Health checks link.
Deploy application container Click Add Readiness probe link.
Deploy application container Enter following inputs then click ✔️ icon.
Path:
/q/health/ready
Port:
8080
Period:
30
Timeout:
10
Deploy application container Click Add Liveness probe link.
Deploy application container Enter following inputs then click ✔️ icon.
Path:
/q/health/live
Port:
8080
Period:
30
Timeout:
10
Deploy application container Click Build configuration link.
Deploy application container Enter following environment variable then click Deployment link.
Name:
MAVEN_MIRROR_URL
Value:
http://nexus.nexus.svc.cluster.local:8081/repository/maven-public/
Note. This will tell Maven in the builder image to use Nexus deployed on the cluster as a Maven Repository instead to speed up build process.
Deploy application container Enter following environment variable. Then click Resource limits link.
Name:
KUBERNETES_NAMESPACE
Value:
userX-super-heroes
whereX
is your user number.
Deploy application container Enter following memory request and limit. Then click Labels link.
Request:
256
Limit:
768
Deploy application container Enter
system=quarkus-super-heroes
then click Create button.Deploy application container
Add application configurations in ConfigMap and Secret objects to application container
Click on rest-villains entity in view area, a panel will show on right hand side. Notice that a build process starts automatically to build source code and container image (you can click View logs to see build logs). By the way, just let it run in background for now. Then click rest-villains link.
Deploy application container Go to Environment tab to add environment variables to application container. Then click Add all from ConfigMap or Secret link.
Deploy application container Select rest-villains-config ConfigMap and rest-villains-config-creds Secret objects, then click Save button. And then go to Topology menu.
Deploy application container Wait for a while until you see dark blue ring surrounds the rest-villains entity. Hover mouse pointer over it, a bubble should show up and say 1 Running which means there is 1 pod running.
Deploy application container
What have you learnt?
How to create ConfigMap object with YAML to keep all application configurations.
How to create Secret object with YAML to keep all secret application configurations.
How to deploy application with existing source codes using OpenShift Build - Source-to-Image (S2I) with following additional configurations:
Application health checks e.g. liveness and readiness probes
Require and limit resource i.e. memory for application
Environment variable for application container
Environment variable for S2I build i.e. Maven Repository setting
User-defined label
Bind configurations from ConfigMap and Secret objects to application container via environment variables.
Change network port to be exposed for application container.
Last updated