Overview

This article outlines key considerations for installing the Kinetic Platform into a customer-managed Kubernetes cluster.

Operations Checklist

Before beginning an installation or upgrade, ensure you’ve confirmed each of the items on the following checklist:

• Kubernetes cluster version compatibility: Before installing or upgrading the Kinetic Platform, customers are responsible for ensuring the compatibility of their Kubernetes cluster version with the Kinetic platform version. Consult the Kinetic Team before upgrading your Kubernetes cluster version.

• Resource management: For your environment, we recommend setting up a three-node cluster with the following resources. Based on usage, you can adjust the size or scale of the cluster as needed:

  • RAM: 32GB per node.
  • CPU: 8-core CPU per node.
  • Storage: A minimum of 100GB storage on all nodes is recommended, as we will provision local storage to manage some operational resources.

What to Know When Setting Up Your Cluster

• CoreDNS customization: The Kinetic Platform cluster configuration process includes customizing the CoreDNS configuration. This process involves adding a rewrite plugin to alter DNS resolution within the cluster for traffic coming from outside the cluster.
  • What to look out for: During the installation process, you'll find a checkbox on the configuration form that allows opting out of the automatic deletion of the existing config map to deploy a new one with the necessary customizations. In some cases, your existing cluster may require a different method for including these customizations, such as another Configuration Map or Secret. Customers are responsible for ensuring these customizations are applied. Please consult the Kinetic Platform team for further details or assistance with applying these customizations manually. It is crucial to ensure that manual customizations are not overwritten by Platform upgrades or Kubernetes version upgrades.
• The Nginx Ingress controller: The Kinetic Platform installation process requires deploying an Ingress controller that manages external traffic, directing it to the appropriate service within the cluster. It is configured to expose HTTPS traffic on port 30443 and HTTP traffic on port 30080. To make the Kinetic Platform accessible via a load balancer, these ports must be exposed from the cluster to your load balancer.
  • What to look out for: If you prefer to use your own Nginx Controller, reach out to Kinetic Support for assistance with this customization.