Multi-Cluster

Operational Scalability

In modern infrastructure environments, DevOps often handles Distributed environments. Kudashai solves the "kubeconfig context switching" problem with a UI that unifies everything.

All clusters, from On-Premises, AWS EKS, GCP GKE, to Azure AKS, can be registered centrally in Kudashai. You can also assign tags (Cluster Labels) to distinguish between production, staging, or dev environments.

Management Mode Options

Kudashai provides cluster management options tailored to your infrastructure scale.

Standalone (Single User)

Ideal for local or personal management. Data is stored locally on your device.

By default, Standalone runs in Open mode (without login). If you want to use Secured mode (with a login screen), you simply need to set the admin account credentials in your terminal session or operating system before running the application.

Example in Linux/MacOS terminal:

export KUDASHAI_BOOTSTRAP_ADMIN_USERNAME="your_admin_name"
export KUDASHAI_BOOTSTRAP_ADMIN_PASSWORD="your_secret_password"

# Then run Kudashai
./kudashai

After running these commands, Kudashai will detect the credentials and automatically enable the login feature on the Dashboard.

Platform (Multi-Tenant & Multi-User)

Ideal for team-scale operations (DevOps Teams). This mode unlocks Enterprise-grade capabilities, including:

• Role-Based Access Control (RBAC): Assigns access rights with a strict hierarchy across 4 role levels:

  • Superadmin: Full control over the entire platform.
  • Admin: Manages cluster operations and internal user management (only for Member and Viewer roles).
  • Member: Active user who can manage Kubernetes resources.
  • Viewer: Read-only user who can only view (monitoring).

  Permissions Matrix:

  Capability / Feature	Superadmin	Admin	Member	Viewer
  Cluster Management (Add/Remove Kubeconfig)	✅	✅	❌	❌
  User Management (Create/Edit/Delete)	✅	✅	❌	❌
  K8s Mutations (Apply, Scale, Restart, Delete)	✅	✅	✅	❌
  AI Configuration (Add Providers/API Keys)	✅	✅	✅	❌
  Port Forwarding (Desktop version only)	✅	✅	✅	❌
  AI Chat & Diagnostics	✅	✅	✅	✅
  View Audit Trail	✅	✅	❌	❌

• Audit Trail (Audit Log System): Designed to meet Enterprise-class compliance and forensic standards. Every user activity is recorded precisely, covering the following data matrix:

  Audit Trail Data Matrix:

  Data Component	Recorded Description
  Actor (User)	The identity of the user performing the activity (e.g., johndoe@email.com).
  Category & Action	The type of operation executed, divided into categories: Auth, Cluster, K8s Mutating, User Management, AI Config, Port Forward.
  Target Resource	The specific object modified, such as a Pod name, Deployment type, or another user account.
  Cluster Location	The specific cluster where the Kubernetes resource mutation occurred.
  Network Data	Originating IP Address and User-Agent type of the user's browser.
  Additional Context	JSON metadata containing the change payload (useful for seeing specific altered data).
  Time & Status	Exact Timestamp (time zone) along with execution status: Success or Failure.

  Note: The audit log retention period is adjustable (default 90 days) via the System Settings menu.

How to Enable Platform Mode: If you already have a license or are part of the AwanIO ecosystem, you do not need to manually install a database. You can use our built-in tool, Kudashai Studio.

Through the Kudashai Studio interface, simply enter your App Key (license key). The system will perform an automatic handshake to activate Platform mode and dynamically connect your Dashboard to a secure centralized database.