-
Bug
-
Resolution: Done
-
Blocker
-
camel-quarkus-2.2-GA
-
None
- Use OCP 4.6/4.8
- # Installed Application Services Metering Operator - see image operator_running.png
- Clone quickstart - https://github.com/jboss-fuse/camel-quarkus-examples/tree/camel-quarkus-examples-2.2.0-product/file-bindy-ftp and apply following diff
~/R/q/c/file-bindy-ftp ❯❯❯ git diff camel-quarkus-examples-2.2.0-product ✭ ✱ diff --git a/file-bindy-ftp/src/main/resources/application.properties b/file-bindy-ftp/src/main/resources/application.properties index 2516fbc7935..9648f7f7a7a 100644 --- a/file-bindy-ftp/src/main/resources/application.properties +++ b/file-bindy-ftp/src/main/resources/application.properties @@ -50,3 +50,11 @@ quarkus.openshift.build-strategy=docker #quarkus.openshift.resources.requests.cpu=250m #quarkus.openshift.resources.limits.memory=512Mi #quarkus.openshift.resources.limits.cpu=1000m + + +quarkus.openshift.labels."com.company"=Red_Hat +quarkus.openshift.labels."rht.comp"=Camel-Quarkus +quarkus.openshift.labels."rht.comp_ver"=2.2.0 +quarkus.openshift.labels."rht.prod_name"=Red_Hat_Integration +quarkus.openshift.labels."rht.prod_ver"=2021-Q4 +quarkus.openshift.labels."rht.subcomp_t"=application
- Deploy the quickstart with
mvn clean package -DskipTests -Dquarkus.kubernetes.deploy=true -Dquarkus.kubernetes-client.trust-certs=true
- Check the pod is running - see labels_in_pod.jpg
- Wait few mintues (i was waiting more then 10mins) and check the Montoring -> Metrics and try to gather metrics - see no_endpoints.png
- blocks
-
ENTESB-17085 Provide metering labels for Camel Quarkus
- Closed