Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

karmada-io

@karmada-io source repo

10 published skills

  1. ▌
    Karmada Dashboard Quickstart · karmada-io
    QuickStart for getting the Karmada Dashboard running on an existing kind-based Karmada dev environment and exposing it for access. Use when asked to bring up / install / start the dashboard following the README QuickStart, especially on a kind cluster or a cloud VM (e.g. Oracle Cloud) where the dashboard must be reachable from another host.
    0
    installs
  2. ▌
    E2e Root Cause Analysis · karmada-io
    Find the root cause of failing or flaky Karmada E2E tests from CI runs. Use when a user reports an e2e test failure, a flaky CI job, or asks to find the root cause of an e2e timeout, providing a GitHub Actions run/job URL, a PR number/URL, or logs.
    0
    installs
  3. ▌
    Generating Release Notes · karmada-io bundle
    Use when preparing changelogs or release notes from merged pull requests for a patch, minor, or preview release.
    0
    installs
  4. ▌
    Karmada Search · karmada-io bundle
    Use when a Karmada operator needs to inspect karmada-search, search.karmada.io APIService health, ResourceRegistry scope, global search/cache results, proxying behavior, default cache versus OpenSearch, or deployment flags, or when a contributor needs to change Search API, registry storage, cache, proxy, backend, command wiring, or tests. Do not use for local repository search, generic kubectl queries, policy YAML, scheduler placement, controller-manager ownership, or propagation failures before Search is isolated.
    0
    installs
  5. ▌
    Karmada Knowledge · karmada-io bundle
    Use when a Karmada user, operator, or platform engineer needs Karmada domain understanding: architecture, components, APIs, scheduling concepts, propagation object flow, failover concepts, push versus pull mode, global view, or Karmada multi-region modeling. Do not use for non-Karmada product behavior, policy YAML creation/review, one observed placement decision, live propagation debugging, Search operations, controller-manager triage, code implementation, repository text search, release lookup, or knowledge-base maintenance.
    0
    installs
  6. ▌
    Karmada Audit Policy · karmada-io bundle
    Use this skill when the user provides or points to Karmada PropagationPolicy, ClusterPropagationPolicy, OverridePolicy, or ClusterOverridePolicy YAML and wants validation, review, risk analysis, or corrections. Audit schema and admission rules, selector scope, placement and replica semantics, priority and preemption, override patches, and runtime-dependent assumptions with source-backed findings. Do not use it primarily to generate a policy from new intent, explain one observed placement, debug live propagation, or update the skill knowledge base.
    0
    installs
  7. ▌
    Karmada Create Policy · karmada-io bundle
    Use when a Karmada user or platform engineer asks to create PropagationPolicy, ClusterPropagationPolicy, OverridePolicy, or ClusterOverridePolicy YAML, or requests explicit field or value changes to those policy objects. Do not use when the primary task is reviewing or auditing supplied policy YAML for problems.
    0
    installs
  8. ▌
    Karmada Debug Propagation · karmada-io bundle
    Use when a Karmada user, operator, or platform engineer has a concrete propagation incident where a known workload, ResourceBinding or ClusterResourceBinding, Work, member object, or status update failed, is missing, or is stale across member clusters. Do not use for policy creation, static YAML review, explaining cluster or replica placement choices, Search incidents, controller-manager restart/flag/role/ownership questions before controller-manager is ruled in or out, general architecture, website lookup, or knowledge maintenance.
    0
    installs
  9. ▌
    Karmada Explain Placement · karmada-io bundle
    Use this skill when a Karmada user, operator, or platform engineer asks why a concrete ResourceBinding or ClusterResourceBinding selected, rejected, ordered, or assigned replicas to specific member clusters. Use it for observed placement outcomes from full or partial evidence, including prose descriptions when binding YAML or runtime logs are unavailable; in partial cases bound conclusions and request the missing objects. Do not use it for policy creation, static YAML audit, general scheduling concepts, post-scheduling Work/member failures, live mutations, or knowledge maintenance.
    0
    installs
  10. ▌
    Karmada Controller Manager · karmada-io bundle
    Use when a Karmada operator needs to inspect or rule out karmada-controller-manager process health, controller enablement, leader election, runtime flags, logs, events, or ownership, or when a contributor needs to add or change a controller, option, flag, registration, test, or RBAC wiring in karmada-controller-manager. Use karmada-debug-propagation for a generic end-to-end workload incident unless the request explicitly targets controller-manager ownership or implementation. Do not use for kube-controller-manager, Search internals, scheduler-only placement, or policy YAML.
    0
    installs