Опишете задачата
Към всички skills

frontend-forge-fe-operations

kubesphere · Разработка

Operate FrontendExtension (FE) resources in frontend-forge: create, update, rebuild, inspect package artifacts, download packages, publish, unpublish, delete, and debug package/publish controller behavior. Use this skill whenever the user mentions FE operations, FrontendExtension lifecycle, extension package/download/publish/unpublish, artifact ConfigMaps, package Jobs, publisher Jobs, publish target ConfigMaps or Secrets, rebuild-token, package-state/publish-state labels, or troubleshooting FE

Оригинален текст · няма потвърден превод на български
Платформи: ClaudeНиво: НапредналоВ индекса: 11.06.2026 г.Обновен в GitHub: 15.07.2026 г.

Теми: agent-skills · ai · cloud-native · cncf · devops · ebpf · hacktoberfest · kubernetes · kubesphere · llm · multi-cluster · multi-tenancy · observability · servicemesh · skills

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
17 057
Лиценз
NOASSERTION
Последна проверка на записа
20.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add kubesphere/kubesphere

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

Frontend Forge FE Operations

When to use

Use this skill for operational work around FrontendExtension resources:

  • Create or update an FE manifest
  • Trigger or inspect package generation
  • Force a rebuild with the rebuild-token annotation
  • Download the generated package artifact
  • Publish, unpublish, or delete an extension
  • Inspect FE status, conditions, labels, Jobs, artifact ConfigMaps, and publish targets
  • Debug FE package phases such as Packaging, Ready, and Failed, plus publish/unpublish phases such as Pending, Running, Succeeded, and Failed

If the task is about FrontendIntegration runtime JSBundle creation, use the FI operations skill instead. FE package/publish does not create a runtime JSBundle in the current cluster.

Quick Entry

  • Create or update FE -> read references/lifecycle.md
  • Rebuild package -> read references/lifecycle.md
  • Publish, unpublish, delete-with-unpublish, list through API, or download -> read references/api.md
  • Inspect package Job, artifact ConfigMap, publish Job, labels, or conditions -> read references/inspection.md
  • Debug stuck or failed state -> read references/inspection.md, then check controller logs

Preconditions

  • The current Kubernetes context is pointed at the target cluster.
  • The FE CRD exists: frontendextensions.frontend-forge.kubesphere.io.
  • The FE controller is installed, usually as the extension-controller component.
  • The FE API is installed when using download, publish, unpublish, or delete-with-unpublish HTTP operations.
  • The build service configured by BUILD_SERVICE_BASE_URL is reachable from package Jobs.
  • Publish target data exists when publishing, normally ConfigMap/ksbuilder-publish-config in extension-frontend-forge.

Source of truth

Prefer live cluster state for operations and repo docs for expected behavior:

  • kubectl get fe <name> -o yaml
  • kubectl get jobs -n <work-namespace> -l frontend-forge.kubesphere.io/fe-name=<name>
  • spec/frontend-extension-design.md
  • spec/crds.md
  • spec/k8s-resources.md
  • config/samples/frontendextension-inspecttask.yaml
  • crates/api/src/fe.rs
  • crates/frontend-extension-controller
  • crates/frontend-forge-extension-api

Resource Model

Целият SKILL.md в GitHub