k8s-conventions

Securing Kubernetes manifests requires setting resource requests and limits, applying Pod Security Standards, configuring security contexts, implementing default-deny NetworkPolicies, and enforcing RBAC roles to prevent misconfigurations and security gaps.

You validate Kubernetes manifests in CI by running validation tools like kubeconform and kube-score against your YAML files before merging to enforce conventions, check schema validity, and catch security gaps early in the deployment pipeline.

Yes, the Skill applies conventions across Deployments, Services, RBAC, and NetworkPolicies to guide review and implementation in production clusters, ensuring proper access control and default-deny network traffic rules are enforced.

You should use the app.kubernetes.io/* label taxonomy to standardize manifest structure and metadata. This ensures consistent labeling across Deployments, Services, Namespaces, and ConfigMaps for maintainable production cluster resources.

You enforce Pod Security Standards and resource limits by applying manifest conventions that require proper security contexts, define resource requests and limits, and validate configurations using kube-score and kubeconform before merging changes.

You should apply Kubernetes manifest conventions when creating Deployments, Services, Namespaces, and ConfigMaps to prevent misconfigurations, enforce default-deny NetworkPolicies, and maintain secure, consistent environments across production clusters.