-
Notifications
You must be signed in to change notification settings - Fork 86
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
Configuring service-dns fails when installed from helm chart #58
Comments
I tried the same and it does not work. However, when I fetched the helm chart and modified locally, |
I checked that one again and I see it is similar to that issue. Apparently, When you do local values.yaml
It is good so far but then we receive an exception with that configuration and it is thrown by Hazelcast.
Apparently, we do not allow null passing in yaml files to Hazelcast Configuration. |
I had a quick chat with @blazember |
The workaround for this (or maybe even a proper solution) is to set I think we'll not introduce |
Hi,
I get always the exception
For completeness, I'm using Hazelcast 3.12.6 (same behavior also with the 3.12.5) deployed with its helm chart version 2.10.0 on a Rancher cluster (version 2.2.8). # Hazelcast custom Helm chart template
---
image:
repository: "nexus.internal/hazelcast/hazelcast"
tag: "3.12.6"
cluster:
memberCount: 1
metrics:
enabled: true
rbac:
enabled: false
serviceAccount:
create: false
mancenter:
enabled: false
hazelcast:
yaml:
hazelcast:
group:
name: tomcat
network:
join:
kubernetes:
enabled: true
service-dns: ${serviceName}.${namespace}.svc.cluster.local
service-name: (note again the white space after the ":" of This is the configmap containing the "hazelcast.yaml" file created by the helm chart: apiVersion: v1
data:
hazelcast.yaml: |-
hazelcast:
group:
name: tomcat
management-center:
enabled: ${hazelcast.mancenter.enabled}
url: ${hazelcast.mancenter.url}
network:
join:
kubernetes:
enabled: true
namespace: ${namespace}
resolve-not-ready-addresses: true
service-dns: ${serviceName}.${namespace}.svc.cluster.local
service-name: null
multicast:
enabled: false
rest-api:
enabled: true
endpoint-groups:
HEALTH_CHECK:
enabled: true
kind: ConfigMap
metadata:
creationTimestamp: "2020-02-12T16:04:44Z"
labels:
app.kubernetes.io/instance: hazelcast
app.kubernetes.io/managed-by: Tiller
app.kubernetes.io/name: hazelcast
helm.sh/chart: hazelcast-2.10.0
io.cattle.field/appId: hazelcast
name: hazelcast-configuration
namespace: hazelcast
resourceVersion: "22916230"
selfLink: /api/v1/namespaces/hazelcast/configmaps/hazelcast-configuration
uid: 62b1514b-4db1-11ea-b80a-00505682af12 You can see that Of course, by setting either:
Hazelcast claims about the incorrect usage of Any idea/feedback? |
I think we need to fix it in the |
Created an issue in hazelcast-kubernetes: hazelcast/hazelcast-kubernetes#197 |
The workaround for this issue is to create |
Let's close it when Hazelcast |
Fixed by #170 It should work fine starting from the chart version |
When run the Hazelcast server using helm chart with service-dns value configured fails with the following error
Caused by: com.hazelcast.config.InvalidConfigurationException: Properties 'service-dns' and ('service-name' or 'service-label-name') cannot be defined at the same time
I override the config properties from the parent chart as follows
I tried overriding the service-name property to null but it is still not working.
The text was updated successfully, but these errors were encountered: