-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem in detecting server port in application.yaml unlike application.properties where it detect the server port when k8s:resources #2909
Comments
@AhmdFahad : Hello, do you think your problem is related to #2832 ? Did you run |
yes i did , |
You can check presence of |
It seems like the issue is related to the .yaml extension. But when I used .yml, it worked well. |
I think I've understood what the problem is. I hope it gets resolved soon. I'll go ahead and close this ticket, and thank you for your assistance |
@AhmdFahad : What does spring documentation advise? Is it |
@rohanKanojia , In fact, I'm not entirely sure what the preference is, but in the documentation, YAML is referenced 45 times compared to YML, which is only mentioned 17 times.https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#features.spring-application look at that quoted from Documentation This is what I couldn't reach, but if you have the knowledge, I hope you can share it with me. |
@AhmdFahad : I think problem is here in our code: We only consider for |
Describe the bug
here when it create kubernetes manifest it did`n detect the port
unlike in application.properties it detect the port
Eclipse JKube version
1.16.2
Component
Kubernetes Maven Plugin
Apache Maven version
other (please specify in additional context)
Gradle version
None
Steps to reproduce
mvn clean install k8s:resource
Expected behavior
.
Runtime
Kubernetes (vanilla), other (please specify in additional context)
Kubernetes API Server version
other (please specify in additional context)
Environment
Windows
Eclipse JKube Logs
No response
Sample Reproducer Project
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: