create-database

Provision PostgreSQL or MariaDB databases with replicas and credential secrets in Kube-DC projects.

34|5|Updated Mar 5, 2025
One-click install
npx skills add https://github.com/kube-dc/kube-dc-public --skill create-database-kube-dc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-database
Source: https://github.com/kube-dc/kube-dc-public/tree/main/skills/create-database
Command: npx skills add https://github.com/kube-dc/kube-dc-public --skill create-database-kube-dc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provisioning databases for Kube-DC projects is error-prone and complex, requiring consistent templates, credentials management, and correct exposure settings to support workloads across environments.

Core Features & Use Cases

  • Automated database provisioning: Create PostgreSQL or MariaDB instances with templates, versions, and HA-ready replicas.
  • Credential and secret handling: Auto-create and expose secrets for workloads to securely connect with proper host, port, and database name.
  • Flexible exposure and access patterns: Attach internal access by default, with optional gateway or load balancer exposure for external workloads.
  • Use Case: Deploy a new database for a microservice in project-namespace with automatic connection details available to the app.

Quick Start

Create a new KdcDatabase in the target project with the desired engine, version, replicas, and exposure settings.

Frequently Asked Questions about create-database

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

FAQPage Schema
How do I provision a highly available PostgreSQL or MariaDB database for a Kube-DC microservice?

You provision a highly available PostgreSQL or MariaDB database by creating a KdcDatabase in your target project, configuring the engine, version, and replicas to ensure HA readiness for your microservice.

How are database credentials and connection secrets managed when provisioning databases in Kube-DC?

Database credentials are managed through automatic secret creation, generating secrets that securely expose the host, port, and database name so workloads can connect without manual credential handling.

Can I expose a provisioned MariaDB or PostgreSQL instance externally from a Kube-DC project?

Provisioned databases support flexible exposure patterns, attaching internal access by default with optional gateway or load balancer exposure for external workloads.

What database engines and configuration options are supported for workload provisioning in Kube-DC?

Supported database engines include PostgreSQL and MariaDB, with configurable options for engine versions, replicas, storage, and exposure settings to match typical workload requirements.

Does Kube-DC database provisioning support isolated instances with automatic credential generation?

Yes, Kube-DC provisioning automates the creation of isolated PostgreSQL or MariaDB databases with automatic credential secret generation for secure workload connections.