kubesphere-core

KubeSphere core API routing works by redirecting user requests to appropriate sub-skills based on intent, orchestrating tasks to cluster-management, multi-tenant-management, or extension-management. It applies to environments managing Kubernetes clusters, tenants, and extensions.

Central API routing for multi-tenant Kubernetes environments works by redirecting user requests to the kubesphere-multi-tenant-management sub-skill. It coordinates core services and extensions, exposing the relationship between the LuBan-based engine and extensions for architecture visibility.

Yes, the requests library is required as a dependency to use this Skill. It provides the common API routing utilities and interfaces required to coordinate API interactions between core KubeSphere services and extensions.

Yes, you can use the included scripts component to orchestrate KubeSphere extension management tasks. The routing utility delegates requests to kubesphere-extension-management, coordinating extensions via common API interfaces.

The best way to manage multi-cluster operations in KubeSphere is through central API routing, which delegates user intents directly to the kubesphere-cluster-management sub-skill. This approach satisfies core architecture routing and API delegation for Kubernetes clusters.

If your KubeSphere API request routes to the wrong sub-skill, verify the user intent matches the routing orchestration rules for kubesphere-cluster-management, kubesphere-multi-tenant-management, or kubesphere-extension-management. The utility relies on intent-based delegation to select the correct target.