Changing the default port of the embedded server does not change the K8S probes default port

[waynemorphic]

I was checking out the Spring Boot Quickstart provided under the Maven package and found something peculiar that I would like a little help with. The default port of the embedded server is 8080. However, I changed it to 8081 underresources\application.yaml with the configuration:

server:
  port: 8081

This follows that, building the Spring Boot application with mvn spring-boot:run serves the application on Tomcat's port 8081.

2024-03-16 18:55:29.067  INFO 3498 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8081 (http)
2024-03-16 18:55:29.085  INFO 3498 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2024-03-16 18:55:29.085  INFO 3498 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.82]
2024-03-16 18:55:29.210  INFO 3498 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2024-03-16 18:55:29.210  INFO 3498 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1614 ms
2024-03-16 18:55:29.870  INFO 3498 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'
2024-03-16 18:55:29.974  INFO 3498 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8081 (http) with context path ''
2024-03-16 18:55:29.987  INFO 3498 --- [           main] o.e.j.m.sample.spring.boot.Application   : Started Application in 3.102 seconds (JVM running for 3.656)

However, when running the command that creates K8S resources descriptors, i.e mvn clean k8s:resource -Pkubernetes, then there is a discrepancy between the ports:

[INFO] k8s: jkube-controller: Adding a default Deployment
[INFO] k8s: jkube-service: Adding a default service 'spring-boot' with ports [8081]
[INFO] k8s: jkube-healthcheck-spring-boot: Adding readiness probe on port 8080, path='/actuator/health', scheme='HTTP', with initial delay 10 seconds
[INFO] k8s: jkube-healthcheck-spring-boot: Adding liveness probe on port 8080, path='/actuator/health', scheme='HTTP', with initial delay 180 seconds
[INFO] k8s: jkube-service-discovery: Using first mentioned service port '8081' 

What I have tried so far with the invaluable help of @rohanKanojia was adding the following property in my POM file:

<properties>
    <jkube.version>${project.version}</jkube.version>
    <jkube.generator.spring-boot.webPort>8081</jkube.generator.spring-boot.webPort>
  </properties>

However, the above port discrepancy persists. Guidance on this will be helpful. Thank you

[manusa]

This seems like a bug

[vaibhavp3]

Is it resolved, still facing the similar issue, it doesn't replace default ports for web and jolokia.
Thanks

[rohanKanojia]

@vaibhavp3 : It was due to not running mvn package see #2832 (comment)

[vaibhavp3]

Thanks for the quick response.
Apparently it still adds jolokia and prometheus ports. Ran mvn package && mvn k8s:resource but still see following in generated manifest.
- containerPort: 9779 name: prometheus protocol: TCP - containerPort: 8778 name: jolokia protocol: TCP
Configured these properties to disable adding default port in manifest since they are conflicting with the ones declared in deployment.yaml file.
<jkube.generator.java-exec.jolokiaPort>0</jkube.generator.java-exec.jolokiaPort> <jkube.generator.java-exec.prometheusPort>0</jkube.generator.java-exec.prometheusPort>

[vaibhavp3]

Got it, it was supposed to be jkube.generator.spring-boot.webPort. Thanks!