Generic Provider

​

Supported Add-Ons

• Headlamp: Provides a Kubernetes dashboard UI for the cluster.
• AWS Workload Identity: Allows your pods to assume AWS IAM Roles.
• AWS ECR: Allows pulling images from private ECR registries.
• Local Path Storage: Creates PVCs backed by local volumes.
• Logs: Enables logging for pods and cluster auditing.
• CPLN Platform: Installs a BYOK location into the cluster, so Control Plane workloads run on its servers.

​

Step 1 - Server Setup

1. Prepare the servers: Create at least one server that meets the following server requirements:
   • Server requirements:
     • Linux kernel version higher than 5.4
     • Minimum CPU: 1 core
     • Minimum RAM: 512 MB
   • Servers require internet egress access.
   • Ensure you have SSH access to the servers.

​

Step 2 - Create a Managed Kubernetes Cluster with a Manifest

1. Optionally update the manifest below and save it as generic-mk8s-template.yaml.

kind: mk8s
name: generic-mk8s-example
description: generic-mk8s-example mk8s in gcp-us-east1
tags: {}
spec:
  provider:
    generic:
      location: gcp-us-east1
      nodePools:
        - name: general
          labels:
            environment: generic-mk8s-example
          taints: []
  addOns:
    headlamp: {}
    localPathStorage: {}
    awsWorkloadIdentity: {}
  firewall:
    - description: default
      sourceCIDR: 0.0.0.0/0
  version: 1.35.3

• Add-ons: Includes Headlamp, Local Path Storage, and AWS Workload Identity.
• Location: The cluster’s Kubernetes control plane will be managed in the gcp-us-east1 location. Placing worker nodes close to the control plane is recommended for optimal performance.
• Kubernetes API Firewall: Uses the default rule, allowing public access to the Kubernetes API. It is advisable to restrict API access to a known IP range for security purposes.
• Kubernetes Version: 1.35.3.
• Node Pool: A single general node pool.

2. Create the Cluster: Deploy the generic-mk8s-example cluster by applying the manifest.
   • CLI: Execute cpln apply -f generic-mk8s-template.yaml --org YOUR_ORG_HERE.
   • Console: Apply the generic-mk8s-template.yaml file using the >_ apply option in the upper right corner.
   Wait until the cluster is initialized: rerun cpln mk8s health generic-mk8s-example until it reports READY as true.

​

Step 3 - Connect the Servers

1. Obtain the Join Script:
   • Using the CLI: a. Save the Join Script to a file: Execute the command cpln mk8s join generic-mk8s-example --type join-script --options nodePoolName=general > join_general.sh.
   • Using the UI: a. Navigate to the Control Plane Console: Visit the Control Plane Console. b. Access the Dashboard: In the Control Plane Console, navigate to Kubernetes in the left sidebar panel, click on the generic-mk8s-example cluster, and go to Node Pools. Click on More on the right side of the general Node Pool and select Generate Join Script.
2. Copy and Execute the Script on the Server: Connect to the remote server and execute the join script. After the execution, the server should be joined to the cluster as a node under the general node pool. Repeat these steps for all necessary servers.

​

Step 4 - Accessing the Cluster

​

1. Using the Terminal

1. Obtain the cluster’s kubeconfig file: Execute the command cpln mk8s kubeconfig generic-mk8s-example -f /tmp/generic-mk8s-example-conf.
2. Access the cluster with kubectl: Use the obtained kubeconfig file by running export KUBECONFIG=/tmp/generic-mk8s-example-conf for the current shell session.

​

2. Using Headlamp

1. Navigate to the Control Plane Console: Visit the Control Plane Console.
2. Open Headlamp: In the Control Plane Console, navigate to Kubernetes in the left sidebar panel and click on Headlamp under Dashboard for the cluster generic-mk8s-example.

​

Advanced Configuration Options

​

Networking

spec:
  provider:
    generic:
      location: gcp-us-east1
      networking:
        serviceNetwork: 192.168.0.0/16
        podNetwork: 172.16.0.0/15
        dnsForwarder: 8.8.8.8 8.8.4.4
      nodePools:
        - name: general

​

Ingress IPs

spec:
  provider:
    generic:
      nodePools:
        - name: general
          labels:
            cpln.io/allowPrivateIPs: 'true'
            cpln.io/allowTailscaleIPs: 'true'

kubectl label node NODE_NAME cpln.io/allowPrivateIPs=true cpln.io/allowTailscaleIPs=true

​

Overriding the Ingress IP

spec:
  addOns:
    byok:
      location: //location/YOUR_LOCATION
      config:
        actuator:
          env:
            INGRESS_IP_AZ_1: 203.0.113.10