You can expose Management Center outside Kubernetes to remotely manage your Hazelcast deployment.
Management Center supports several options for external access.
Configure external access
Operator supports the following configuration for Management Center external access.
| Field | Description |
|---|---|
|
Management Center external access methods:
|
|
Ingress exposes HTTP and HTTPS routes from outside the Kubernetes cluster to Management Center. Traffic routing is controlled by rules defined on the Ingress resource. |
|
An OpenShift Container Platform Route exposes a service at a host name so that external clients can reach it by name. |
Example Management Center load balancer configuration
The following example exposes Management Center using a dedicated load balancer.
apiVersion: hazelcast.com/v1alpha1
kind: ManagementCenter
metadata:
name: managementcenter
spec:
repository: "hazelcast/management-center"
licenseKeySecretName: hazelcast-license-key
externalConnectivity:
type: LoadBalancer
hazelcastClusters:
- address: hazelcast
name: dev
Example Management Center ingress configuration
The following example exposes Management Center using Ingress.
apiVersion: hazelcast.com/v1alpha1
kind: ManagementCenter
metadata:
name: managementcenter
spec:
repository: "hazelcast/management-center"
licenseKeySecretName: hazelcast-license-key
externalConnectivity:
type: ClusterIP
ingress:
hostname: "example.hostname"
ingressClassName: nginx
path: "/mancenter"
annotations:
nginx.ingress.kubernetes.io/enable-opentelemetry: "true"
hazelcastClusters:
- address: hazelcast
name: dev
Example Management Center route configuration
The following example exposes Management Center using the default OpenShift Container Platform Route.
apiVersion: hazelcast.com/v1alpha1
kind: ManagementCenter
metadata:
name: managementcenter
spec:
repository: "hazelcast/management-center"
licenseKeySecretName: hazelcast-license-key
externalConnectivity:
type: ClusterIP
route:
hostname: ""
hazelcastClusters:
- address: hazelcast
name: dev