Add parameters for more Hazelcast cluster configs such as HD and WAN Replication

[hazelcast]

Add parameters for more Hazelcast cluster configs such as HD and WAN Replication

[mesutcelik]

Hi @johnmdesjardins
Can you give more concrete example here?

For instance, I can start hazelcast-enterprise with openssl giving following parameters. I see it is very flexible in that sense because certificate related params are not even defined in values.yaml file. That means you can pass any hazelcast configuration you want via setters.

I would personally prefer to pass hazelcast.xml or hazelcas.yaml to the helm chart instead of passing so many parameters.

helm install --name my-release-ssl \
  --set hazelcast.licenseKey=<license-key>  \
  --set hazelcast.ssl=true \
  --set secretsMountName=keystore \
  --set hazelcast.yaml.hazelcast.network.ssl.factory-class-name=com.hazelcast.nio.ssl.OpenSSLEngineFactory \
  --set hazelcast.yaml.hazelcast.network.ssl.properties.keyFile=/data/secrets/key.pem \
  --set hazelcast.yaml.hazelcast.network.ssl.properties.trustCertCollectionFile=/data/secrets/cert.pem \
  --set hazelcast.yaml.hazelcast.network.ssl.properties.keyCertChainFile=/data/secrets/chain.pem \
  hazelcast/hazelcast-enterprise

Let me know what you think so that we close this issue.

[johnmdesjardins]

You can close the issue. Based on your example, I agree. Also, given the added ability to use YAML this also makes us more friendly to use with Helm.

On Oct 30, 2019, at 12:23 PM, Mesut Celik ***@***.***> wrote: Hi @johnmdesjardins <https://github.com/johnmdesjardins> Can you give more concrete example here? For instance, I can start hazelcast-enterprise with openssl giving following parameters. I see it is very flexible in that sense because certificate related params are not even defined in values.yaml file. That means you can pass any hazelcast configuration you want via setters. I would personally prefer to pass hazelcast.xml or hazelcas.yaml to the helm chart instead of passing so many parameters. helm install --name my-release-ssl \ --set hazelcast.licenseKey=<license-key> \ --set hazelcast.ssl=true \ --set secretsMountName=keystore \ --set hazelcast.yaml.hazelcast.network.ssl.factory-class-name=com.hazelcast.nio.ssl.OpenSSLEngineFactory \ --set hazelcast.yaml.hazelcast.network.ssl.properties.keyFile=/data/secrets/key.pem \ --set hazelcast.yaml.hazelcast.network.ssl.properties.trustCertCollectionFile=/data/secrets/cert.pem \ --set hazelcast.yaml.hazelcast.network.ssl.properties.keyCertChainFile=/data/secrets/chain.pem \ hazelcast/hazelcast-enterprise Let me know what you think so that we close this issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9?email_source=notifications&email_token=AC4LGI3YUEQN625O4WFMZMLQRGYJBA5CNFSM4F7QDIO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECU27NA#issuecomment-547991476>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC4LGI5XPGMV6MGOXUDL6R3QRGYJBANCNFSM4F7QDIOQ>.

John DesJardins VP Solution Architecture & CTO N. America [email protected] Hazelcast Inc. [email protected] +1.770.833.9256 Skype: john.m.desjardins

[mesutcelik]

👍