Validate OpenShift and Helm manifests for Emerald platform compliance.
npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-emerald
Please help me install this Agent Skill. Skill: bc-gov-emerald Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/bc-gov-emerald Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-emerald
Prevents silent traffic drops, CI gate failures, and runtime misconfigurations by documenting Emerald-specific OpenShift requirements such as AVI route annotations, DataClass pod labels, PriorityClass enforcement, storage selection, and Helm settings so reviewers and engineers can apply consistent platform controls.
Use bc-gov-emerald to validate a Helm chart or manifest for Emerald compliance by checking aviinfrasetting annotations, DataClass and Internet-Ingress labels, global.openshift, PriorityClass presence, StorageClass, and Route termination rules.
High-intent search queries and answers about installing and using this skill.
Emerald compliance validation checks Helm charts for required aviinfrasetting annotations, DataClass and Internet-Ingress pod labels, global.openshift: true, and PriorityClass presence. This ensures deployments pass platform policy gates and avoid silent traffic drops on BC Gov OpenShift clusters.
ERR_EMPTY_RESPONSE on Emerald typically indicates incorrect aviinfrasetting annotation values or missing Internet-Ingress pod labels. Default-deny NetworkPolicy behavior drops traffic unless routes use the correct private or public VIP settings to restore connectivity.
Required pod labels for Emerald policy gates include DataClass, owner, environment, and Internet-Ingress. These labels satisfy ag-devops Datree and Conftest rules while aligning with default-deny NetworkPolicy expectations to prevent silent traffic drops.
Configuring StatefulSets on Emerald requires adding a PriorityClass and selecting the netapp-file-standard StorageClass. These settings ensure proper pod scheduling priority and storage provisioning, preventing runtime misconfigurations during OpenShift deployment.
Yes, deploying Helm charts to BC Gov Emerald mandates setting global.openshift: true. This flag configures chart templates for OpenShift-specific security and routing constraints, ensuring Deployments and StatefulSets pass CI gating and platform policy controls.
Emerald DNS split-tunneling limitations cause name resolution differences between internal cluster and external networks, complicating route troubleshooting. Awareness of this behavior is essential when triaging connectivity issues alongside default-deny NetworkPolicy enforcement.
kcns008Generate Kubernetes and OpenShift YAML manifests from templates with security defaults.
rloisellAuthor and validate Kubernetes NetworkPolicy manifests for OpenShift clusters.
rloisellValidate Emerald OpenShift Helm charts and ArgoCD manifests against BC Government policies.
rloisellAutomate Vault secrets management for Emerald OpenShift deployments.
