Connecting to a Hazelcast Cluster

To connect Management Center to a Hazelcast cluster, you need to configure at least the name of the cluster and the addresses of one or more members.

You can connect Management Center to a cluster that is configured to use TLS.

See Management Center Documentation for more detailed information.

Configuring Cluster Connections

Connection configuration for the Hazelcast clusters that Management Center will monitor.

Field	Description
hazelcastClusters[].address	IP address or DNS name of the Hazelcast cluster. If the cluster is exposed with a service name in a different namespace, use the following syntax <service-name>.<service-namespace>.
hazelcastClusters[].name	Name of the Hazelcast cluster that Management Center will connect to, default is dev.
hazelcastClusters[].tls.secretName	Specifies the name of Kubernetes TLS secret.

warning

hazelcastClusters field does not support deleting clusters from the custom resource. If you want to remove a cluster from the Management Center, you can do it from the Management Center UI.

Example Management Center configuration

The example configuration below does the following:

• Configuring connection to a Hazelcast cluster using hazelcast DNS name
• Use dev Hazelcast cluster name

yaml

apiVersion: hazelcast.com/v1alpha1
kind: ManagementCenter
metadata:
  name: managementcenter
spec:
  repository: "hazelcast/management-center"
  licenseKeySecretName: hazelcast-license-key
  hazelcastClusters:
    - address: hazelcast
      name: dev

Example Management Center with TLS Configuration

The example configuration below does the following:

• Configuring connection to a Hazelcast cluster using hazelcast DNS name
• Use dev Hazelcast cluster name
• Connect to Hazelcast cluster with TLS certificate defined in example secret

yaml

apiVersion: hazelcast.com/v1alpha1
kind: ManagementCenter
metadata:
  name: managementcenter
spec:
  repository: 'hazelcast/management-center'
  licenseKeySecretName: hazelcast-license-key
  hazelcastClusters:
  - address: hazelcast
    name: dev
    tls:
      secretName: example

You can create TLS secret from existing PEM certificate:

shell

kubectl create secret generic example \
  --from-file=tls.crt=example.crt \
  --from-file=tls.key=example.key