Console
Quick Start Cluster Namespace Application Helm Apps F.A.Q

ON-Board Existing Cluster

Onboarding an existing cluster involves tagging your Kubernetes cluster with the Krack8 platform. By tagging your cluster, you can manage your Kubernetes cluster resources through the Krack8 console.

There are a few prerequisites required to tag your Kubernetes cluster with the Krack8 platform. You can find these in our console.

Inputs

Cluster name: Define a cluster name the cluster will be tagged with this name on the Krack8 platform.

NGINX and Volume Config:

Ingress Controller

To access the required platform components in your cluster, the operator will set up a Kubernetes Ingress. For this Ingress to work, an ingress controller must be installed. you need to configure a load balancer to make the cluster accessible from outside. Additionally, the platform requires an ingress class, which helps Kubernetes determine which Ingress controllers should handle incoming network traffic to the services.

If your cluster doesn't have an Ingress controller installed, please click here for the official documentation on how to set up ingress.

Note:

Currently, the platform supports only NGINX and HAProxy ingress controllers.

Domain Configuration

For onboarding the cluster, the platform requires a wildcard domain pointing to the ingress controller's load balancer for external access. The platform will create subdomains under the provided wildcard domain. You need to configure your domain to point to the External IP of the Kubernetes service (type: LoadBalancer) associated with your ingress controller.

If you prefer an SSL-enabled connection (HTTPS), you can provide TLS certificates for the wildcard domain. Alternatively, you can manage the certificates by installing a cert-manager on your cluster and creating a certificate for the domain through it. The platform can also use the secret name created by cert-manager that contains the certificate details. To install cert-manager on your cluster, follow the instructions in the official documentation

Storage Information

The platform requires Kubernetes Storage Class details to create and manage volumes in your cluster. Please provide two storage classes: one with ReadWriteOnce access mode and another with ReadWriteMany access mode. For Official documents, please go through the link: https://kubernetes.io/docs/concepts/storage/storage-classes

To On-board an Existing cluster user will need to go to the Cluster-> On -Board Existing K8 cluster

Users will see all essential requirements such as Kubernetes, Kubectl, Helm, Fetch Operator Helm Chart, Ingress Controller, domain Configuration, Storage Information (All Guidelines are available).

Optional requirements are also listed with guidelines and commands which are not mandatory.

From the Cluster information tab users can provide the cluster information to onboard the existing cluster.

Required Information:

General Information

  • Cluster Name
  • Namespace

Ingress Information

  • Domain Name (Wildcard Supported)
  • NGINX
  • Ingress Class
  • SSL Config
  • Additional Ingress Configuration

Storage Information

  • Storage Class (Read Write Once)
  • Storage Class (Read Write Many)

User can Also add additional information if needed:

  • Prometheus Server Configuration
  • Grafana configuration
  • Loki Server Configuration
  • ArgoCD Configuration
  • Enable Service Mesh

Click on the next button to go to the next step to review the information and the cluster onboard process will be started.

It will take 8-10 minutes to complete the onboarding process.

Once onboard is completed, the user will need to go to the Cluster Menu and select the cluster. Copy the helm command and run the command in your desired cloud provider’s Kubernetes cluster which you want to onboard. Once the command is executed successfully the kc-agent-operator will establish an on-board your cluster in the Krack8 control panel.