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:Platform config
Under Settings → Platform config you can view and edit your cluster’s Platform Config — the declarative tool stack (GitOps, ingress, certificates, monitoring, secrets, and more) that the operator keeps in sync. Every change you save is written back to the connected Git repository, and the GitOps engine applies it to the cluster.Blueprints
To create applications and services on your cluster from pre-configured Helm charts, use Blueprints. Blueprints provide sensible defaults that you can review and customize before deploying, and support optional GitOps integration. Platform Config and Blueprints cover two distinct roles: the Platform Config manages the cluster’s shared platform tool stack (the admin’s job), while Blueprints create applications on top of it (what the user does).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.