-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Quarkus will crash when specified the environment variable QUARKUS_KUBERNETES_CONFIG_SECRETS_ENABLED #36622
Comments
Hello ! I'll try to have a look at this issue if no one is already on it. |
Go for it! |
@rysurd thanks, but this is already fixed in the latest Quarkus version. @cuichenli please, update to Quarkus 3.5.0. Thanks! |
It's not released yet, we will release it tomorrow :). |
@radcortez thanks for the info. do you know in which pr we got this issue fixed? just want to know why this is happening. thanks! |
Yes I'd interested too in knowing how this was fixed :) |
This was introduced in smallrye/smallrye-config#984 and later fixed by smallrye/smallrye-config#1000 as part of some work to improve memory allocation. |
Describe the bug
according to the document https://quarkus.io/guides/kubernetes-config#quarkus-kubernetes-config_quarkus.kubernetes-config.secrets.enabled
this environment variable should match the config for quarkus.kubernetes-config.secrets.enabled
But the actual case is whenever this environment variable is provided, quarkus will fail to start with the following error messages:
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
https://github.com/cuichenli/quarkus-buggy-environment-variable
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.4.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: