Kubernetes Orchestrators

Orchestrators allow you to connect the administration console to your Kubernetes clusters to deploy and manage PeSIT Wizard servers.

Add an Orchestrator

Via the Interface

1. Go to Orchestrators
2. Click Add Orchestrator
3. Fill in the connection information
4. Click Create

Supported Orchestrator Types

Type	Description
K3S	K3s (Rancher) - Lightweight Kubernetes
K8S	Standard Kubernetes
EKS	Amazon Elastic Kubernetes Service
GKE	Google Kubernetes Engine
AKS	Azure Kubernetes Service

Authentication

In-Cluster

For deployments where the admin runs in the same cluster:

k8sAuthType: IN_CLUSTER

No additional configuration required.

Bearer Token

k8sAuthType: TOKEN
k8sToken: "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9..."

Client Certificate

k8sAuthType: CERTIFICATE
k8sClientCert: |
  -----BEGIN CERTIFICATE-----
  ...
  -----END CERTIFICATE-----
k8sClientKey: |
  -----BEGIN PRIVATE KEY-----
  ...
  -----END PRIVATE KEY-----
k8sCaCert: |
  -----BEGIN CERTIFICATE-----
  ...
  -----END CERTIFICATE-----

Advanced Configuration

Skip TLS Verify

For development environments with self-signed certificates:

k8sSkipTlsVerify: true

Warning

Never use in production!

MetalLB IP Range

For K3s clusters with MetalLB:

metalLbIpRange: "192.168.1.200-192.168.1.250"

Test the Connection

After creating an orchestrator, test the connection:

1. Select the orchestrator
2. Click Test Connection
3. Verify that the status changes to "Connected"

Best Practices

1. One orchestrator per environment: Separate dev, staging, prod
2. Use dedicated ServiceAccounts: Create a SA with minimal permissions
3. Token rotation: Renew tokens regularly
4. Access audit: Enable Kubernetes auditing