diff --git a/camel-quarkus/README.md b/camel-quarkus/README.md index 147b607..407dbcb 100644 --- a/camel-quarkus/README.md +++ b/camel-quarkus/README.md @@ -11,6 +11,7 @@ This project uses Quarkus [Container Images](https://quarkus.io/guides/container The most important part in terms of the _hawtio-enabled_ configuration is defined in the `` section. To make it _hawtio-enabled_, the Jolokia agent must be attached to the application with HTTPS and SSL client authentication configured. The client principal should match those the Hawtio Online instance provides (the default is `hawtio-online.hawtio.svc`). ```xml + https * 8778 @@ -19,6 +20,7 @@ The most important part in terms of the _hawtio-enabled_ configuration is define cn=hawtio-online.hawtio.svc true false + ``` ## How to run locally diff --git a/camel-springboot/README.md b/camel-springboot/README.md index 2433757..7eccc50 100644 --- a/camel-springboot/README.md +++ b/camel-springboot/README.md @@ -11,14 +11,26 @@ This project uses JKube [kubernetes-maven-plugin](https://eclipse.dev/jkube/docs All you need to make the application _hawtio-enabled_ is to define additional environment variables to the deployment resource to fine-tune the Jolokia agent options. By default, JKube plugin sets up a Jolokia agent with HTTPS and SSL client authentication enabled. The only necessary configurations are the client principal that matches the Hawtio Online instance (the default is `hawtio-online.hawtio.svc`) and the CA cert to specify `service-ca.crt` instead of the default `ca.crt`. ```xml - - - - cn=hawtio-online.hawtio.svc - caCert=/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt - - - + + org.eclipse.jkube + kubernetes-maven-plugin + ${kubernetes-maven-plugin-version} + + + + + cn=hawtio-online.hawtio.svc + caCert=/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt + + + + ``` ## How to run locally