cd

Generates a hardened Helm chart for deploying Spring Boot microservices to Kubernetes.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/oriddd/ai-toolkit --skill cd-oriddd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cd
Source: https://github.com/oriddd/ai-toolkit/tree/main/copilot/public/skills/cd
Command: npx skills add https://github.com/oriddd/ai-toolkit --skill cd-oriddd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing Kubernetes deployment manifests for every microservice is repetitive and error-prone, especially when enforcing security hardening, health probes, autoscaling, and monitoring consistently across services. ## Core Features & Use Cases - Helm Chart Generation: Creates a complete helm-chart/ directory with Chart.yaml, values.yaml, and templates for Deployment, Service, HPA, ServiceAccount, ServiceMonitor, and Secret. - Security Hardening by Default: Enforces non-root containers, read-only root filesystems, dropped capabilities, seccomp profiles, and disabled service account token automounting. - Observability Integration: Wires liveness/readiness probes to Spring Actuator health endpoints and adds a Prometheus ServiceMonitor scraping the actuator metrics endpoint. - Use Case: A team finishing a new Spring Boot service needs production-grade Kubernetes manifests; this Skill generates the full chart with hardened security contexts and probes, leaving only registry and resource values to fill in. ## Quick Start Ask the AI to apply the cd skill to generate a Helm chart for your Spring Boot service with your chart name, port, context path, and image registry.

Frequently Asked Questions about cd

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

FAQPage Schema
How do I create a Helm chart for a Spring Boot microservice?

Provide the chart name, application port, context path, and image registry, and the Skill generates a complete helm-chart directory with Deployment, Service, HPA, ServiceAccount, ServiceMonitor, and Secret templates based on hardened defaults.

How to configure Kubernetes liveness and readiness probes for Spring Boot?

The generated Deployment configures liveness and readiness probes against the Spring Actuator endpoints at {contextPath}/actuator/health/liveness and {contextPath}/actuator/health/readiness on the application port.

Does the Helm chart support Prometheus monitoring?

Yes, it includes a ServiceMonitor template for the Prometheus Operator that scrapes the {contextPath}/actuator/prometheus endpoint exposed by Spring Actuator on the main application port.

Can I use this chart inside an umbrella Helm chart?

Yes, the chart includes a helper.images.registryName template helper so parent umbrella charts can override the image registry through .Values.global.imageRegistry while still working standalone.

What security settings does the generated Deployment enforce?

The Deployment runs as non-root with configurable UID/GID, uses a read-only root filesystem, drops all capabilities, disallows privilege escalation, applies seccomp RuntimeDefault, and disables service links and host namespaces.

When should I not use this Helm chart skill?

Avoid it when your platform requires organization-specific registries, shared ConfigMaps, or custom runtime conventions baked in; those should be added as local overrides rather than modifying the vendor-neutral templates.