vault-secrets

Automate Vault secrets management for Emerald OpenShift deployments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Vault Secrets Shared Skill standardizes secrets management across BC Gov projects on Emerald, reducing fragmentation and misconfigurations in secret handling.

Core Features & Use Cases

  • Vault path convention and standardized secret naming
  • External Secrets Operator patterns for Kubernetes secret synchronization
  • Vault Agent Injector annotations for in-cluster secret injection
  • GitHub Actions integration for CI-time secret retrieval
  • Helm templates for shape-only secrets

Quick Start

Configure a new project by applying the Vault path conventions and ESO integration.

Frequently Asked Questions about vault-secrets

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

FAQPage Schema
How do I standardize Vault secrets management across OpenShift deployments?

Standardizing Vault secrets on OpenShift involves applying consistent Vault path conventions, External Secrets Operator patterns, and Vault Agent Injector annotations to reduce fragmentation across project deployments.

What is the best way to integrate Vault with the External Secrets Operator in Kubernetes?

Integrating Vault with the External Secrets Operator involves applying standardized patterns that synchronize secrets from Vault into Kubernetes secrets, ensuring consistent access and naming conventions across your clusters.

How do I retrieve Vault secrets during a GitHub Actions CI pipeline?

Retrieving Vault secrets during GitHub Actions CI pipelines requires integrating specific secret retrieval patterns that securely fetch and inject necessary credentials at build time without exposing them in logs.

Can I use Helm templates for shape-only secrets when deploying to OpenShift?

Yes, you can use Helm templates for shape-only secrets in OpenShift deployments to define the required secret structure and schema without embedding the actual sensitive values directly in your Helm charts.

Do I need Vault Agent Injector annotations for in-cluster secret injection?

Vault Agent Injector annotations are needed for in-cluster secret injection to automatically populate application pods with secrets directly from Vault upon startup, eliminating the need for manual mounting.

How do I bootstrap a new OpenShift project with standardized Vault path conventions?

Bootstrapping a new OpenShift project with Vault path conventions involves applying standardized naming structures for secret storage and access patterns to ensure projects are securely configured from the start.