Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/kubernetes-deployment-creator/skills/creating-kubernetes-deployments

creating-kubernetes-deployments

Unverified

Deploy 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/service_template.yaml

View on GitHub
# Kubernetes Service Manifest Template
# This file defines a Kubernetes Service, which exposes your application to the network.

apiVersion: v1
kind: Service
metadata:
  name: example-value-service # Replace with your service name
  namespace: default # Change if you're using a different namespace
  labels:
    app: example-value # Replace with your application name
    tier: frontend # Or backend, database, etc.
spec:
  type: ClusterIP #  Options: ClusterIP, NodePort, LoadBalancer
                  #  ClusterIP: Exposes the service on a cluster-internal IP. Choose this if you only need access from within the cluster.
                  #  NodePort:  Exposes the service on each Node's IP at a static port (the NodePort). Choose this for external access during development.
                  #  LoadBalancer: Exposes the service externally using a cloud provider's load balancer.  Choose this for production external access.
  selector:
    app: example-value #  Must match the labels of your deployment's pods
  ports:
    - port: 80 # The port the service exposes internally
      targetPort: 8080 # The port your application is listening on within the pod
      protocol: TCP
      name: http # Optional, but helpful for clarity
  # sessionAffinity: ClientIP # Uncomment this line to enable session affinity (sticky sessions) based on the client's IP address.  Useful for applications that require session persistence.
  # externalTrafficPolicy: Cluster # Uncomment for LoadBalancer.  Options: Cluster or Local.  Local preserves the client source IP.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall