[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78C6G71B3M15BCZGP1PXWW7":3,"skill-same:01M78C6G71B3M15BCZGP1PXWW7":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M78C6G71B3M15BCZGP1PXWW7","gke-multitenancy",null,"Plans and configures multi-tenancy on GKE. Covers namespace isolation, RBAC planning for teams, resource quotas, LimitRanges, network isolation, and cost allocation. Use when designing GKE multi-tenancy, configuring GKE namespaces, setting up resource quotas, or isolating GKE teams. Don't use for single-tenant cluster configuration or general deployment instructions (use gke-basics or gke-app-onboarding instead).","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgke-multitenancy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gke-multitenancy\ndescription: >-\n  Plans and configures multi-tenancy on GKE. Covers namespace isolation, RBAC\n  planning for teams, resource quotas, LimitRanges, network isolation, and\n  cost allocation. Use when designing GKE multi-tenancy, configuring GKE\n  namespaces, setting up resource quotas, or isolating GKE teams. Don't use\n  for single-tenant cluster configuration or general deployment instructions\n  (use gke-basics or gke-app-onboarding instead).\nmetadata:\n  category: Containers\n---\n\n# GKE Multi-Tenancy\n\nThis reference covers enterprise multi-tenancy patterns on GKE, including\nnamespace isolation, RBAC planning, resource quotas, and network segmentation.\n\n> **MCP Tools:** `apply_k8s_manifest`, `get_k8s_resource`, `check_k8s_auth`,\n> `describe_k8s_resource`, `delete_k8s_resource`\n\n## When to Use\n\n-   Multiple teams sharing a single GKE cluster\n-   Isolating workloads by environment (dev\u002Fstaging\u002Fprod) within one cluster\n-   Implementing least-privilege access control\n-   Cost allocation across teams or projects\n\n## Multi-Tenancy Models\n\n| Model                         | Isolation    | Complexity | Cost           |\n| ----------------------------- | ------------ | ---------- | -------------- |\n| **Namespace-per-team**        | Soft (RBAC + | Low        | Lowest (shared |\n:                               : Network      :            : cluster)       :\n:                               : Policy)      :            :                :\n| **Namespace-per-environment** | Soft         | Low        | Low            |\n| **Node pool-per-team**        | Medium       | Medium     | Medium         |\n:                               : (dedicated   :            :                :\n:                               : compute)     :            :                :\n| **Cluster-per-team**          | Hard (full   | High       | Highest        |\n:                               : isolation)   :            :                :\n\n> **Golden path recommendation**: Start with namespace-per-team for cost\n> efficiency. Escalate to stronger isolation only when compliance requires it.\n\n## Namespace Isolation Setup\n\n### 1. Create Namespaces\n\n```bash\nkubectl create namespace team-a\nkubectl create namespace team-b\nkubectl label namespace team-a team=a\nkubectl label namespace team-b team=b\n```\n\n### 2. RBAC Configuration\n\n**Principle**: Grant minimal permissions per namespace. Never bind to\n`system:authenticated`.\n\n```yaml\n# Namespace-scoped role for a team\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  name: team-a-developer\n  namespace: team-a\nrules:\n- apiGroups: [\"\", \"apps\", \"batch\"]\n  resources: [\"pods\", \"deployments\", \"services\", \"configmaps\", \"jobs\"]\n  verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\", \"delete\"]\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  name: team-a-developers\n  namespace: team-a\nsubjects:\n- kind: Group\n  name: \"team-a@example.com\"  # Google Group\n  apiGroup: rbac.authorization.k8s.io\nroleRef:\n  kind: Role\n  name: team-a-developer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n**RBAC best practices:** Use Google Groups for subject bindings. Prefer\nnamespace-scoped Roles over ClusterRoles. See the `gke-security` skill for full\nRBAC hardening guidance.\n\n### 3. Resource Quotas\n\nPrevent any single team from consuming all cluster resources:\n\n```yaml\napiVersion: v1\nkind: ResourceQuota\nmetadata:\n  name: team-a-quota\n  namespace: team-a\nspec:\n  hard:\n    requests.cpu: \"10\"\n    requests.memory: \"20Gi\"\n    limits.cpu: \"20\"\n    limits.memory: \"40Gi\"\n    pods: \"50\"\n    services: \"10\"\n    persistentvolumeclaims: \"10\"\n```\n\n### 4. LimitRanges\n\nSet default and maximum resource constraints per container:\n\n```yaml\napiVersion: v1\nkind: LimitRange\nmetadata:\n  name: team-a-limits\n  namespace: team-a\nspec:\n  limits:\n  - type: Container\n    default:\n      cpu: \"500m\"\n      memory: \"512Mi\"\n    defaultRequest:\n      cpu: \"100m\"\n      memory: \"128Mi\"\n    max:\n      cpu: \"4\"\n      memory: \"8Gi\"\n```\n\n> [!IMPORTANT] **Mandatory Defaults**: When defining `min` or `max` limits in a\n> `LimitRange`, you **must** also define corresponding `default` and\n> `defaultRequest` values. If you set a `min` or `max` without defaults, any pod\n> deployed without explicit resource requests\u002Flimits will be rejected by the\n> admission controller.\n\n### 5. Network Isolation\n\nApply default-deny per namespace (see the `gke-security` skill), then allow\nintra-team traffic:\n\n```yaml\n# Allow same-namespace pods to talk + DNS\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-same-namespace\n  namespace: team-a\nspec:\n  podSelector: {}\n  ingress:\n  - from:\n    - podSelector: {}\n  egress:\n  - to:\n    - podSelector: {}\n  - to:  # Allow DNS\n    - namespaceSelector: {}\n      podSelector:\n        matchLabels:\n          k8s-app: kube-dns\n    ports:\n    - protocol: UDP\n      port: 53\n```\n\n## Cost Allocation\n\n### Labels for Cost Attribution\n\n```bash\n# Label namespaces for billing\nkubectl label namespace team-a cost-center=engineering\nkubectl label namespace team-b cost-center=data-science\n```\n\n### GKE Cost Allocation\n\nEnable GKE cost allocation to break down costs by namespace and label:\n\n```bash\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-cost-allocation\n```\n\nView in Cloud Billing > GKE Cost Allocation.\n","# GKE Multi-Tenancy\n\nThis reference covers enterprise multi-tenancy patterns on GKE, including\nnamespace isolation, RBAC planning, resource quotas, and network segmentation.\n\n> **MCP Tools:** `apply_k8s_manifest`, `get_k8s_resource`, `check_k8s_auth`,\n> `describe_k8s_resource`, `delete_k8s_resource`\n\n## When to Use\n\n-   Multiple teams sharing a single GKE cluster\n-   Isolating workloads by environment (dev\u002Fstaging\u002Fprod) within one cluster\n-   Implementing least-privilege access control\n-   Cost allocation across teams or projects\n\n## Multi-Tenancy Models\n\n| Model                         | Isolation    | Complexity | Cost           |\n| ----------------------------- | ------------ | ---------- | -------------- |\n| **Namespace-per-team**        | Soft (RBAC + | Low        | Lowest (shared |\n:                               : Network      :            : cluster)       :\n:                               : Policy)      :            :                :\n| **Namespace-per-environment** | Soft         | Low        | Low            |\n| **Node pool-per-team**        | Medium       | Medium     | Medium         |\n:                               : (dedicated   :            :                :\n:                               : compute)     :            :                :\n| **Cluster-per-team**          | Hard (full   | High       | Highest        |\n:                               : isolation)   :            :                :\n\n> **Golden path recommendation**: Start with namespace-per-team for cost\n> efficiency. Escalate to stronger isolation only when compliance requires it.\n\n## Namespace Isolation Setup\n\n### 1. Create Namespaces\n\n```bash\nkubectl create namespace team-a\nkubectl create namespace team-b\nkubectl label namespace team-a team=a\nkubectl label namespace team-b team=b\n```\n\n### 2. RBAC Configuration\n\n**Principle**: Grant minimal permissions per namespace. Never bind to\n`system:authenticated`.\n\n```yaml\n# Namespace-scoped role for a team\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  name: team-a-developer\n  namespace: team-a\nrules:\n- apiGroups: [\"\", \"apps\", \"batch\"]\n  resources: [\"pods\", \"deployments\", \"services\", \"configmaps\", \"jobs\"]\n  verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\", \"delete\"]\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  name: team-a-developers\n  namespace: team-a\nsubjects:\n- kind: Group\n  name: \"team-a@example.com\"  # Google Group\n  apiGroup: rbac.authorization.k8s.io\nroleRef:\n  kind: Role\n  name: team-a-developer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n**RBAC best practices:** Use Google Groups for subject bindings. Prefer\nnamespace-scoped Roles over ClusterRoles. See the `gke-security` skill for full\nRBAC hardening guidance.\n\n### 3. Resource Quotas\n\nPrevent any single team from consuming all cluster resources:\n\n```yaml\napiVersion: v1\nkind: ResourceQuota\nmetadata:\n  name: team-a-quota\n  namespace: team-a\nspec:\n  hard:\n    requests.cpu: \"10\"\n    requests.memory: \"20Gi\"\n    limits.cpu: \"20\"\n    limits.memory: \"40Gi\"\n    pods: \"50\"\n    services: \"10\"\n    persistentvolumeclaims: \"10\"\n```\n\n### 4. LimitRanges\n\nSet default and maximum resource constraints per container:\n\n```yaml\napiVersion: v1\nkind: LimitRange\nmetadata:\n  name: team-a-limits\n  namespace: team-a\nspec:\n  limits:\n  - type: Container\n    default:\n      cpu: \"500m\"\n      memory: \"512Mi\"\n    defaultRequest:\n      cpu: \"100m\"\n      memory: \"128Mi\"\n    max:\n      cpu: \"4\"\n      memory: \"8Gi\"\n```\n\n> [!IMPORTANT] **Mandatory Defaults**: When defining `min` or `max` limits in a\n> `LimitRange`, you **must** also define corresponding `default` and\n> `defaultRequest` values. If you set a `min` or `max` without defaults, any pod\n> deployed without explicit resource requests\u002Flimits will be rejected by the\n> admission controller.\n\n### 5. Network Isolation\n\nApply default-deny per namespace (see the `gke-security` skill), then allow\nintra-team traffic:\n\n```yaml\n# Allow same-namespace pods to talk + DNS\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-same-namespace\n  namespace: team-a\nspec:\n  podSelector: {}\n  ingress:\n  - from:\n    - podSelector: {}\n  egress:\n  - to:\n    - podSelector: {}\n  - to:  # Allow DNS\n    - namespaceSelector: {}\n      podSelector:\n        matchLabels:\n          k8s-app: kube-dns\n    ports:\n    - protocol: UDP\n      port: 53\n```\n\n## Cost Allocation\n\n### Labels for Cost Attribution\n\n```bash\n# Label namespaces for billing\nkubectl label namespace team-a cost-center=engineering\nkubectl label namespace team-b cost-center=data-science\n```\n\n### GKE Cost Allocation\n\nEnable GKE cost allocation to break down costs by namespace and label:\n\n```bash\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-cost-allocation\n```\n\nView in Cloud Billing > GKE Cost Allocation.\n",{"name":5,"metadata":24,"description":7},{"category":25},"Containers","main","be3de0244dc1a57e323d8160787ebb40fb64930e","skills\u002Fgoogle\u002Fcloud\u002Fgke-multitenancy","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Solizardking\u002Fskillhub-main --skill gke-multitenancy",{"tool":41,"command":42},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill gke-multitenancy",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill gke-multitenancy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgke-multitenancy\u002FSKILL.md",true,[],[50,57,64,71,78,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]