原则
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 运维部署
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Kubernetes Principles
Use this skill as standing guidance for this domain. Apply the checklist first; read the detailed reference only when the task is substantial, risky, unfamiliar, or review-oriented.
## Operating Rules
- Prefer the repository's existing conventions, toolchain, and CI commands over generic defaults.
- Make the smallest coherent change that satisfies the request while preserving behavior.
- Treat tests, linting, dependency hygiene, and security review as part of completion.
- If a principle conflicts with higher-priority repository instructions or an explicit user request, follow the higher-priority instruction and call out the tradeoff.
## Core Checklist
- Set requests, limits, probes, disruption budgets, and rollout strategy deliberately for production workloads.
- Use namespace boundaries, least-privilege RBAC, and network policies for isolation.
- Follow Kubernetes Pod Security Standards; default application workloads toward the Restricted profile.
- Run containers as non-root, drop unnecessary capabilities, and avoid host namespaces and privileged containers.
- Store configuration in ConfigMaps and secrets appropriately; do not commit plaintext secrets.
- Validate Helm templates, CRDs, and manifests against schemas and policy before applying.
- Use labels and annotations consistently for ownership, observability, selection, and lifecycle automation.
- Design upgrades and rollbacks before changing stateful workloads, ingress, storage, or networking.
## Validation
Run applicable checks when they exist in the project; if a tool is missing, report that it was skipped.
- `helm lint` for charts
- `helm template ... | kubeconform -strict` or schema validation for rendered manifests
- Policy checks with Kyverno, Gatekeeper/OPA, Conftest, or the project's admission policy tooling
## Detailed Reference
For the complete principle set with examples and edge cases, read [references/principles.md](references/principles.md) when deeper guidance is useful.
---
> Source: [asciifylabs/asciify-skills](https://github.com/asciifylabs/asciify-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
章节与文件索引
按说明文件中的顺序排列。
操作规则
核心清单
验证
详细参考
文件/命令 -> helm lint · helm template ... | kubeconform -strict · Gatekeeper/OPA · references/principles.md · asciifylabs/asciify-skills · github.com/asciifylabs/asciify-skills
内容校验值 -> 9c28bd1cca26
当前原文的自动摘译,尚未人工审校。
操作规则
与通用默认值相比,更喜欢存储库的现有约定、工具链和 CI 命令。做出最小的一致改变来满足要求,同时保留行为。将测试、linting、依赖性卫生和安全审查视为完成的一部分。如果某个原则与较高优先级的存储库指令或明确的用户请求相冲突,请遵循较高优先级的指令并进行权衡。
核心清单
为生产工作负载特意设置请求、限制、探测、中断预算和部署策略。使用命名空间边界、最低权限 RBAC 和网络策略进行隔离。遵循 Kubernetes Pod 安全标准;默认应用程序工作负载朝向受限配置文件。以非 root 身份运行容器,删除不必要的功能,并避免使用主机命名空间和特权容器。
验证
当项目中存在适用的检查时,运行它们;如果缺少某个工具,请报告它已被跳过。
helm lint用于图表helm template ... | kubeconform -strict或用于渲染清单的模式验证 使用 Kyverno、Gatekeeper/OPA、Conftest 或项目的准入策略工具进行策略检查详细参考
有关包含示例和边缘情况的完整原则集,请在需要更深入的指导时阅读引用/principles.md。来源:asciifylabs/asciify-skills — 由 TomeVault 分发。