Create a DataSurface Yellow Kubernetes Credential

Create Kubernetes secrets for DataSurface Yellow credentials with standardized naming.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/billynewport/demo_cokub_model --skill create-a-datasurface-yellow-kubernetes-credential
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/billynewport/demo_cokub_model/tree/main/.claude/skills/create-k8-credential
Command: npx skills add https://github.com/billynewport/demo_cokub_model --skill create-a-datasurface-yellow-kubernetes-credential

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams standardize and automate the creation of Kubernetes credentials for DataSurface Yellow environments, reducing misconfigurations and manual effort.

Core Features & Use Cases

  • Credential name normalization to Kubernetes-compatible secret names.
  • Guidance on mapping model credentials to environment variables for common credential types (USER_PASSWORD, API_TOKEN, CLIENT_CERT_WITH_KEY, API_KEY_PAIR).
  • Use Case: Set up secrets for merge databases, Git repositories, and data ingestion services in a Kubernetes cluster.

Quick Start

Define a credential (e.g., postgres-demo) and create a corresponding Kubernetes secret with the required keys (USER, PASSWORD, TOKEN, PRIVATE_KEY) following the naming rules described.

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 DataSurface Yellow environments?

Kubernetes secret naming conventions for DataSurface Yellow require normalizing credential names to be Kubernetes-compatible. The skill enforces specific naming rules and maps credential types like USER_PASSWORD, API_TOKEN, and CLIENT_CERT_WITH_KEY to the correct environment variables for your services.

How do I map model credentials to environment variables in Kubernetes?

Kubernetes supports four credential types for DataSurface Yellow: USER_PASSWORD, API_TOKEN, CLIENT_CERT_WITH_KEY, and API_KEY_PAIR. Each type corresponds to specific secret keys like USER, PASSWORD, TOKEN, or PRIVATE_KEY, which are then mapped to environment variables for your services.

What is the best way to standardize Kubernetes secret naming for data services?

To set up Kubernetes credentials for DataSurface Yellow, define your credential name, such as postgres-demo, and create a Kubernetes secret containing the required authentication keys. The skill automatically normalizes the name and maps it to the appropriate environment variables based on the credential type.

When do I need Kubernetes credentials for DataSurface Yellow?

When Kubernetes secret names are not normalized for DataSurface Yellow, misconfigurations occur and services fail to authenticate. Applying strict naming conventions and mapping credentials to environment variables correctly prevents these errors across merge databases and data ingestion services.