SkillAtlasSkill 详情

frontend-integration-yaml

The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management

审核状态：已审核Quality 80Security 100

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件：README.md

抓取于 2026年8月1日

banner

The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management

A+ good first issue follow on Twitter

What is KubeSphere

English | 中文

KubeSphere is a distributed operating system for cloud-native application management, using Kubernetes as its kernel. It provides a plug-and-play architecture, allowing third-party applications to be seamlessly integrated into its ecosystem. KubeSphere is also a multi-tenant container platform with full-stack automated IT operation and streamlined DevOps workflows. It provides developer-friendly wizard web UI, helping enterprises to build out a more robust and feature-rich platform, which includes most common functionalities needed for enterprise Kubernetes strategy, see Feature List for details.

The following screenshots give a close insight into KubeSphere. Please check What is KubeSphere for further information.

WorkbenchProject Resources
CI/CD PipelineApp Store

Demo environment

🎮 KubeSphere Lite provides you with free, stable, and out-of-the-box managed cluster service. After registration and login, you can easily create a K8s cluster with KubeSphere installed in only 5 seconds and experience feature-rich KubeSphere.

🖥 You can view the Demo Video to get started with KubeSphere.

Features

🧩 Extensible Architecture Designed for flexibility, supporting plugin-based extensions and seamless integrations. Easily customize and expand functionalities to meet evolving needs. Learn more.
🕸 Provisioning Kubernetes Cluster Support deploy Kubernetes on any infrastructure, support online and air-gapped installation. Learn more.
🔗 Kubernetes Multi-cluster Management Provide a centralized control plane to manage multiple Kubernetes clusters, and support the ability to propagate an app to multiple K8s clusters across different cloud providers.
🤖 Kubernetes DevOps Provide GitOps-based CD solutions and use Argo CD to provide the underlying support, collecting CD status information in real time. With the mainstream CI engine Jenkins integrated, DevOps has never been easier. Learn more.
🔎 Cloud Native Observability Multi-dimensional monitoring, events and auditing logs are supported; multi-tenant log query and collection, alerting and notification are built-in. Learn more.
🌐 Service Mesh (Istio-based) Provide fine-grained traffic management, observability and tracing for distributed microservice applications, provides visualization for traffic topology. Learn more.
💻 App Store Provide an App Store for Helm-based applications, and offer application lifecycle management on Kubernetes platform. Learn more.
💡 Edge Computing Platform KubeSphere integrates KubeEdge to enable users to deploy applications on the edge devices and view logs and monitoring metrics of them on the console. Learn more.
🗃 Support Multiple Storage and Networking Solutions
  • Support GlusterFS, CephRBD, NFS, LocalPV solutions, and provide CSI plugins to consume storage from multiple cloud providers.
  • Provide Load Balancer Implementation OpenELB for Kubernetes in bare-metal, edge, and virtualization.
  • Provides network policy and Pod IP pools management, support Calico, Flannel, Kube-OVN
    • ..
    🏢 Multi-Tenancy Isolated workspaces with role-based access control ensure secure resource sharing across multiple tenants. Supports fine-grained permissions and quota management. Learn more.
    🧠 GPU Workloads Scheduling and Monitoring Create GPU workloads on the GUI, schedule GPU resources, and manage GPU resource quotas by tenant.

    Architecture

    KubeSphere 4.x adopts a microkernel + extension components architecture (codename LuBan). The core part (KubeSphere Core) only includes the essential basic functions required for system operation, with independent functional modules split and provided in the form of extension components. Users can dynamically manage the extension components during system operation. With the extension capabilities, KubeSphere can support more application scenarios and meet the needs of different users.

    Architecture

    Latest release

    🎉 KubeSphere v4.1.2 was released! It brings enhancements and better user experience, see the Release Notes For 4.1.2 for the updates.

    Installation

    KubeSphere can run anywhere from on-premise datacenter to any cloud to edge. In addition, it can be deployed on any version-compatible Kubernetes cluster. KubeSphere consumes very few resources, and you can optionally install additional extensions after installation.

    Quick start

    Installing on K8s

    Run the following commands to install KubeSphere on an existing Kubernetes cluster:

    helm upgrade --install -n kubesphere-system --create-namespace ks-core https://charts.kubesphere.io/main/ks-core-1.1.3.tgz --debug --wait

    KubeSphere for hosted Kubernetes services

    KubeSphere is hosted on the following cloud providers, and you can try KubeSphere by one-click installation on their hosted Kubernetes services.

    You can also install KubeSphere on other hosted Kubernetes services within minutes, see the step-by-step guides to get started.

    👨‍💻 No internet access? Refer to the Air-gapped Installation.

    Guidance, discussion, contribution, and support

    You can reach the KubeSphere community and developers via the following channels:

    :hugs: Please submit any KubeSphere bugs, issues, and feature requests to KubeSphere GitHub Issue.

    :heart_decoration: The KubeSphere team also provides efficient official ticket support to respond in hours. For more information, click KubeSphere Online Support.

    Contribution

    Code of conduct

    Participation in the KubeSphere community is governed by the Code of Conduct.

    Security

    The security process for reporting vulnerabilities is described in SECURITY.md.

    Who are using KubeSphere

    The user case studies page includes the user list of the project. You can leave a comment to let us know your use case.



        

    KubeSphere is a member of CNCF and a Kubernetes Conformance Certified platform , which enriches the CNCF CLOUD NATIVE Landscape.

    Agent / MCP / Skill 创作

    低风险

    • 来源需自行核对维护者身份。
    • 未检测到明显脚本安装指令。
    • 未检测到明显外部权限要求。
    • 未检测到高风险命令。
    • 扫描发现：0 条。

    Codex — Git Clone 安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 克隆仓库：git clone https://github.com/kubesphere/kubesphere.git
    3. 将 "skills/frontend-integration-yaml" 文件夹复制到 Codex 的 skills 目录中。
    4. 重启 Codex 让新的 skill 生效。

    Codex — 手动复制安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 从源仓库下载 SKILL.md 及相关文件。
    3. 在 Codex 的 skills 目录中创建新文件夹。
    4. 将所有 skill 文件复制到新文件夹中。
    5. 重启 Codex 让新的 skill 生效。

    Claude Code — Git Clone 安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 克隆仓库：git clone https://github.com/kubesphere/kubesphere.git
    3. 将 "skills/frontend-integration-yaml" 文件夹复制到 Claude Code 的 skills 目录中。
    4. 重启 Claude Code 让新的 skill 生效。

    Claude Code — 手动复制安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 从源仓库下载 SKILL.md 及相关文件。
    3. 在 Claude Code 的 skills 目录中创建新文件夹。
    4. 将所有 skill 文件复制到新文件夹中。
    5. 重启 Claude Code 让新的 skill 生效。

    Cursor — Git Clone 安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 克隆仓库：git clone https://github.com/kubesphere/kubesphere.git
    3. 将 "skills/frontend-integration-yaml" 文件夹复制到 Cursor 的 skills 目录中。
    4. 重启 Cursor 让新的 skill 生效。

    Cursor — 手动复制安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 从源仓库下载 SKILL.md 及相关文件。
    3. 在 Cursor 的 skills 目录中创建新文件夹。
    4. 将所有 skill 文件复制到新文件夹中。
    5. 重启 Cursor 让新的 skill 生效。

    GitHub Copilot — Git Clone 安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 克隆仓库：git clone https://github.com/kubesphere/kubesphere.git
    3. 将 "skills/frontend-integration-yaml" 文件夹复制到 GitHub Copilot 的 skills 目录中。
    4. 重启 GitHub Copilot 让新的 skill 生效。

    GitHub Copilot — 手动复制安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 从源仓库下载 SKILL.md 及相关文件。
    3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
    4. 将所有 skill 文件复制到新文件夹中。
    5. 重启 GitHub Copilot 让新的 skill 生效。

    Windsurf — Git Clone 安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 克隆仓库：git clone https://github.com/kubesphere/kubesphere.git
    3. 将 "skills/frontend-integration-yaml" 文件夹复制到 Windsurf 的 skills 目录中。
    4. 重启 Windsurf 让新的 skill 生效。

    Windsurf — 手动复制安装

    1. 安装前请先查看来源仓库和风险报告。
    2. 从源仓库下载 SKILL.md 及相关文件。
    3. 在 Windsurf 的 skills 目录中创建新文件夹。
    4. 将所有 skill 文件复制到新文件夹中。
    5. 重启 Windsurf 让新的 skill 生效。
    查看 SKILL.md 原文
    name: frontend-integration-yaml
description: Generate canonical FrontendIntegration YAML from a simplified single-menu authoring model for frontend-forge.

    Frontend Integration YAML

    Generate submit-ready FrontendIntegration YAML from a simplified authoring model with one menu and one or more pages.

    When to Use

    • generate FrontendIntegration YAML
    • create a quick integration YAML from a CRD
    • create an iframe based FrontendIntegration YAML
    • convert simplified single-menu config into canonical YAML

    Do Not Use

    • troubleshooting existing FrontendIntegration resources
    • managing enable/disable/delete lifecycle
    • inspecting JSBundle, Job, controller, or status flows
    • editing manifest generation rules
    • handling multi-menu authoring models

    Required Inputs

    Ask the user instead of guessing when any of these are missing:

    • metadata.name
    • menu.displayName
    • menu.placements[]
    • at least one page in pages[]
    • for crdTable: group, version, scope, names.plural
    • for iframe: key and iframe.src

    Authoring Model

    Use the simplified single-menu model as input to the generator:

    • top-level metadata
    • top-level spec for optional passthrough fields
    • top-level menu
    • top-level pages

    Do not author canonical spec.menus[] by hand.

    Workflow

    1. Extract the simplified authoring model.
    2. Fill only safe defaults.
    3. Keep the model in single-menu form.
    4. Run scripts/generate_frontend_integration.py.
    5. Return the generated canonical YAML.

    Rules

    • Treat the generator script as the source of truth.
    • Do not manually reconstruct canonical YAML when the generator is available.
    • Always output canonical kind: FrontendIntegration.
    • Always expand menu.placements[] into spec.menus[].
    • Always derive children from pages[].
    • If any placement is workspace, force all crdTable.scope values to Namespaced.
    • Default menu.icon to GridDuotone when it is omitted.
    • Do not add runtime-managed metadata unless explicitly requested.

    Output

    • Return the generated YAML first, unless explanation is requested.
    • Prefer a single yaml code block.
    • After the YAML, always output this exact guidance line: FrontendIntegration YAML has been generated. Reply 'apply' to deploy it directly.

    发现问题？提交给管理员复核

    评分：

    评论 (0)

    暂无评论，成为第一个评论者吧！