Kubernetes Deployment Patterns
CheckedHelps with Kubernetes, deployment, patterns as part of deploying and managing cloud infrastructure workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add nickcrew/claude-cortex --skill kubernetes-deployment-patterns -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
nickcrew
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned nickcrew/claude-ctx-plugin at bb47af79ad.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- bb47af79ad
- Scanned
- 6 files, 1,271 lines
About this skill
kubernetes-deployment-patterns
What it does
This skill enables AI agents to generate Kubernetes deployment configurations using specific rollout strategies like RollingUpdate, Recreate, and Blue/Green. It ensures applications deploy safely with defined constraints for availability and resource management.
When to use it
- Zero-downtime updates: Implementing RollingUpdate patterns to replace pods gradually without interrupting service traffic.
- Database migrations: Using the Recreate pattern to ensure all instances stop before a deployment, preventing data inconsistency during schema changes.
- High-availability testing: Setting up Blue/Green deployments to switch between stable and new versions instantly for rapid validation.
- Resource-constrained environments: Configuring specific replica counts and update timeouts to prevent cluster overload during scaling events.
Key capabilities
- Generates
kubectl applycommands for various deployment strategies. - Defines
maxSurgeandmaxUnavailableparameters for fine-grained control over rollout speed. - Supports pre-stop hooks and post-start lifecycle actions within deployment manifests.
- Configures readiness probes to ensure new pods pass health checks before traffic is routed.
Example prompts
- "Create a Kubernetes deployment manifest using the RollingUpdate strategy with a maxSurge of 25% and a maxUnavailable of 0."
- "Generate a Recreate deployment configuration for a legacy application that requires zero concurrent instances during updates."
- "Write a Blue/Green deployment setup that routes traffic to the new version only after successful health checks pass."
Tips & gotchas
Ensure your Kubernetes cluster supports the specific deployment strategy you request, as some patterns require additional API server permissions or controller versions. Always test rollout parameters in a staging environment first to verify they align with your actual pod startup times and network latency.