Deploying Cloud Connector on Kubernetes with a Helm Chart

Kubernetes cluster version 1.26 or later

Helm version 3 or later

PersistentVolume provisioner support in the persistence configuration

Set your Nebula credentials and the base-url that points to the connector URL. The base-url must be accessible from the monitored cluster nodes. Below is an example configuration:

    content: |-
      connector:
        cc-url: https://portal.gridgain.com/
        base-url: http://connector.namespace.svc.cluster.local:80
        name: Nebula Cloud Connector
        username: <provide your Nebula username here>
        password: <provide your Nebula password here>

By default Cloud Connector will be exposed to Kubernetes network using ClusterIP service and 80 port. Ensure that port value in the base-url matches the httpPort.

service:
  enabled: true
  httpPort: 80
  type: ClusterIP

If you want to expose your Cloud Connector outside of Kubernetes network (e.g. to monitor GridGain 9 clusters out of Kubernetes network) configure the ingress settings as shown below. The ingress.host must match the base-url parameter from application.properties file provided along with Cloud Connector installation.

ingress:
  enabled: true
  test: false
  hosts:
    - host: "connector.example.io"
      paths:
        - path: "/api/v1/metrics"
        - path: "/api/v1/events"
  tls:
  - hosts:
      - connector.example.io
    secretName: connector.example.io-tls