General Cluster Information
Modify metadata information of your cluster for displaying purposes in your cluster overview.Loadbalancer
If you’re using an ingress controller, you can use this setting to define a default hostname that will be used when you expose a port on a deployment. Fill in the form fields to set up a default domain for your cluster:- Loadbalancer IPs: If an IngressController is running on your cluster, the external loadbalancer IP address of your cluster will usually be filled out automatically. If the IP is not set automatically, you can enter it manually.
- Loadbalancer Host: Enter a hostname for your cluster. Each service on the cluster will be created under a subdomain of this hostname by default. Later, you can set individual domains in the settings of each service.
Connecting your domain
In your DNS settings, create two records of type A:| Type | Name (example) | Target |
|---|---|---|
| A | yourdomain.com | LOADBALANCER_IP |
| A | *.yourdomain.com | LOADBALANCER_IP |
Blueprints
To set up infrastructure services on your cluster (ingress controllers, monitoring, certificate management, etc.), use Blueprints. Blueprints provide pre-configured Helm charts with sensible defaults that you can review and customize before deploying. They replace the previous Cluster Services and support optional GitOps integration.If you previously installed services through Cluster Services, they continue to work as standard Helm releases. No migration is needed. For new installations, use Blueprints instead.