jeremylongshore/tons-of-skills-marketplace / plugins/devops/kubernetes-deployment-creator/skills/creating-kubernetes-deployments
creating-kubernetes-deployments
UnverifiedDeploy applications to Kubernetes with production-ready manifests. Supports Deployments, Services, Ingress, HPA, ConfigMaps, Secrets, StatefulSets, and NetworkPolicies. Includes health checks, resource limits, auto-scaling, and TLS termination. Use when working with creating kubernetes deployments. Trigger with 'creating', 'kubernetes', 'deployments'.
assets/secret_template.yaml
View on GitHub# This YAML file defines a Kubernetes Secret.
# Secrets are used to store sensitive information, such as passwords, API keys, and tokens.
# It's crucial to handle Secrets securely to protect your application.
apiVersion: v1
kind: Secret
metadata:
name: example-value-secret # Replace with a descriptive name for your secret
namespace: default # Consider using a specific namespace for your application
labels:
app: example-value-app # Replace with your application name
tier: backend # Optional: Add a tier label if applicable
annotations:
# Optional: Add annotations for documentation or automation
description: "Secret for example-value application"
type: Opaque # Use Opaque for generic key-value secrets
data:
# Each key-value pair represents a secret.
# The values should be base64 encoded.
# Example:
# my_password: $(echo -n "mysecretpassword" | base64)
#
# IMPORTANT: Never store plaintext secrets in your YAML file.
# Use a secure method to generate and encode the values.
#
# Example using environment variables:
# my_api_key: $(echo -n "$MY_API_KEY" | base64)
# Add your secrets here:
api_key: YOUR_VALUE_HERE # Replace with your base64 encoded API key
database_password: YOUR_VALUE_HERE # Replace with your base64 encoded database password
# Optional: You can use 'stringData' instead of 'data' to provide plaintext values.
# Kubernetes will automatically encode them to base64.
# However, it's generally recommended to encode the values beforehand for security.
#
# stringData:
# username: myuser
# password: mysecretpasswordRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |