-
Notifications
You must be signed in to change notification settings - Fork 99
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
Issue with Kubernetes embedded configuration not picking up environment variables #306
Comments
I get the same message if I try using the Java configuration:
|
@Sreini thanks for reporting the issue. I tried with your configuration using the following deployment and it works as expected:
Could you please check if the env variables are set correctly in your deployment? You can use the following command to see them:
|
I checked the environment variables as you described: HZ_NETWORK_JOIN_KUBERNETES_SERVICENAME=my-service-name however I am still getting in the logs. Is there anything else I might be doing wrong? |
Could you please share your deployment setup with us? Are there any chances in the container image or the configuration? |
It depends how your config is loaded.
|
I am having issues with the hazelcast k8s plugin not picking up the correct configuration.
In my kubernetes deployment I have defined the following environment variables:
In accordance with the guidelines for setting up embedded hazelcast in kubernetes according to this repo and in combination with the official documentation: https://docs.hazelcast.com/imdg/latest/configuration/overriding-configuration-settings.html. However the Service Name does not seem to be picked up. When I start my application I get the following logging:
Specifically, it says right there:
service-name: null
, whereas according to my configuration it should bemy-service-name
The text was updated successfully, but these errors were encountered: