Installation, Checksum Verification & First-Run Setup
Watch the complete end-to-end installation of AetherKube v1.0.0 on Windows and Docker. Learn how to verify SHA256 hashes, initialize the root admin account, and establish your cluster control plane.
Curriculum & Module Catalog
Four core operational tracks for deploying and scaling the AetherKube autonomous platform.
Download & Installation Guide
Complete walkthrough of downloading the official Windows installer (.exe) or Docker Compose bundle, validating cryptographic SHA256 checksums, and launching the control plane.
- Windows Installer (.exe) setup
- Docker Compose deployment
- SHA256 checksum verification
- First-run setup at localhost:8080
First-Run Onboarding & License Activation
Step-by-step walkthrough of the initial root administrator initialization wizard, multi-tenant organization isolation, and activating offline cryptographic licenses.
- Root admin credential provisioning
- Isolated organization identity setup
- Cryptographic license key activation
- Role-based access control (RBAC)
Cluster Connection & Agent Pairing
Connecting remote Kubernetes clusters across Amazon EKS, Azure AKS, Google GKE, and local K3s environments via secure mutual TLS Helm charts and manifests.
- Helm repository setup & installation
- Outbound-only mTLS agent architecture
- Cluster capability autodiscovery
- Fleet health verification
AI Copilot & Incident Remediation
Deep dive into diagnosing CrashLoopBackOff and OOMKilled failures, evaluating dry-run remediation diffs, and configuring Bring-Your-Own-Key AI models.
- Deterministic local rule engine
- Safe dry-run preview & manual gates
- Anti-flapping 300s cooldown timers
- Post-remediation health validation
Autonomous, Air-Gapped Capable & Multi-Tenant Isolated
AetherKube control plane instances run entirely inside your private infrastructure. Organization identity isolation ensures that independent installations operate completely segregated workloads, even when sharing human-readable company names. All cryptographic license keys are verified locally via ECDSA SHA-256 public key signatures without calling out to unapproved third-party networks.