bc-gov-devops

Validate Emerald OpenShift Helm charts and ArgoCD manifests against BC Government policies.

7|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-devops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-gov-devops
Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/bc-gov-devops
Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-devops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams reliably deploy and operate services on the BC Government Emerald OpenShift platform by consolidating platform conventions, preventing policy violations, and reducing deployment failures caused by missing labels, unsafe network policies, or incorrect Helm/chart configuration.

Core Features & Use Cases

  • Helm and chart standards: Enforces required chart layout, values keys, and ag-helm library usage for OpenShift compatibility.
  • Policy-as-code gate: Guides rendering Helm to a single YAML and running Datree, Polaris, kube-linter, and Conftest to block unsafe deployments.
  • Networking and security: Provides NetworkPolicy patterns, required pod labels (DataClass, owner, environment), PriorityClass guidance, and ArgoCD Application CRD examples for GitOps sync.
  • Secrets and registry: Describes Artifactory setup and secure secret usage in OpenShift and CI workflows.

Quick Start

Render your Helm chart into a single YAML file and run the policy-as-code checks (Datree, Polaris, kube-linter, Conftest) to validate before attempting ArgoCD sync.

Frequently Asked Questions about bc-gov-devops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Helm charts for Emerald OpenShift before deploying with ArgoCD?

To validate Helm charts for Emerald OpenShift, render your chart into a single YAML file and run policy-as-code checks using Datree, Polaris, kube-linter, and Conftest to prevent deployment failures before attempting ArgoCD sync.

What pod labels are required for BC Government OpenShift workloads?

Required pod labels for BC Government OpenShift workloads include DataClass, owner, and environment. Enforcing these labels ensures platform convention compliance and prevents policy violations during deployment.

How do I configure ArgoCD Application CRDs for OpenShift GitOps deployments?

Configuring ArgoCD Application CRDs for OpenShift GitOps deployments requires setting sync settings in the manifest. The Skill provides ArgoCD Application CRD examples to establish GitOps sync for Emerald OpenShift projects.

Does the ag-helm library need to be used for all Helm charts on Emerald OpenShift?

Yes, using the ag-helm library is enforced for OpenShift compatibility. The Skill enforces required chart layout, values keys, and ag-helm library usage to maintain consistent Helm chart standards.

Why are my OpenShift deployments failing policy-as-code checks?

Deployments fail policy-as-code checks due to missing pod labels like DataClass, missing priorityClass presence, unsafe NetworkPolicy designs, or incorrect Helm chart configurations that violate Datree, Polaris, or kube-linter rules.

How do I set up Artifactory image registry for OpenShift CI workflows?

Setting up Artifactory for OpenShift CI workflows involves configuring the image registry and secure secret usage. The Skill describes Artifactory setup to ensure secure image pulls within OpenShift and CI pipelines.