Create a DataSurface Yellow Kubernetes Credential

Create Kubernetes secrets for DataSurface Yellow credentials with kubectl.

2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/datasurface/demo1 --skill create-a-datasurface-yellow-kubernetes-credential-datasurface
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create a DataSurface Yellow Kubernetes Credential
Source: https://github.com/datasurface/demo1/tree/main/.claude/skills/create-k8-credential
Command: npx skills add https://github.com/datasurface/demo1 --skill create-a-datasurface-yellow-kubernetes-credential-datasurface

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of Kubernetes secrets for DataSurface Yellow credentials.

Core Features & Use Cases

  • Generate Kubernetes secrets for common credential types (USER_PASSWORD, API_TOKEN, CLIENT_CERT_WITH_KEY, API_KEY_PAIR).
  • Apply standardized Kubernetes secret naming conventions to ensure seamless injection into pods.
  • Validate and apply patterns for environment variable suffixes and namespace scoping.
  • Use Case: Quickly provision credentials for merge databases and Git repositories during environment bootstrapping.

Quick Start

Use the create-k8-credential skill to generate a Kubernetes secret for a credential named 'postgres-demo' with USER and PASSWORD keys. For example: kubectl create secret generic postgres-demo --from-literal=USER=postgres --from-literal=PASSWORD=your_password -n <namespace>

Frequently Asked Questions about Create a DataSurface Yellow Kubernetes Credential

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

FAQPage Schema
How do I create Kubernetes secrets for database credentials using kubectl?

To create Kubernetes secrets for database credentials, use kubectl to generate a generic secret with literal values like USER and PASSWORD. This skill automates that workflow, applying standardized naming conventions for seamless pod injection.

What Kubernetes secret types are supported for environment variable mapping?

Kubernetes secret creation supports USER_PASSWORD, API_TOKEN, CLIENT_CERT_WITH_KEY, and API_KEY_PAIR credential types. The skill uses these types to generate standardized environment variable mappings for your specific credential requirements.

When do I need to provision Kubernetes secrets for merge databases and Git repositories?

You need to provision Kubernetes secrets for merge databases and Git repositories during environment bootstrapping. This skill automates secret creation for these targets, ensuring credentials are available for pod deployment.

Can I use kubectl to generate environment variable mappings for CQRS targets?

Yes, you can use kubectl to generate environment variable mappings for CQRS targets. The skill supports provisioning credentials for CQRS targets by creating Kubernetes secrets with validated environment variable suffixes and namespace scoping.

What naming conventions does Kubernetes require for injecting secrets into pods?

Kubernetes requires standardized secret naming conventions to ensure seamless injection into pods. This skill enforces those naming patterns and validates environment variable suffixes and namespace scoping during the secret creation process.

Does this Kubernetes secret creation process support API key pairs and client certificates?

Yes, the Kubernetes secret creation process supports API_KEY_PAIR and CLIENT_CERT_WITH_KEY credential types. It applies standardized naming conventions to ensure these secrets are correctly provisioned and injected into your pods.