Rke2 Deployment
ListedAutomates RKE2 cluster deployments and upgrades, simplifying Kubernetes infrastructure management for DevOps teams.
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 realsigridjin/kubespray-skills --skill rke2-deployment -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
sigridjineth
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 failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: 192.168.56.11, get.rke2.io.
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.
Hosts contacted
get.rke2.ioundeclared192.168.56.11undeclaredWhat it found (3 of 7)
- rke2-deployment/SKILL.md:151contacts get.rke2.io
curl -sfL https://get.rke2.io --output install.sh - rke2-deployment/SKILL.md:158contacts get.rke2.io
curl -sfL https://get.rke2.io | INSTALL_RKE2_CHANNEL=v1.33 sh - - rke2-deployment/SKILL.md:388contacts get.rke2.io
curl -sfL https://get.rke2.io | INSTALL_RKE2_TYPE="agent" INSTALL_RKE2_CHANNEL=v1.33 sh -
No credential access: failed
Touches credential material in 6 places.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found (3 of 6)
- rke2-deployment/SKILL.md:337Kubernetes credentials
cp /etc/rancher/rke2/rke2.yaml ~/.kube/config - rke2-deployment/SKILL.md:338Kubernetes credentials
chmod 600 ~/.kube/config - rke2-deployment/SKILL.md:348Kubernetes credentials
scp root@<server-ip>:/etc/rancher/rke2/rke2.yaml ~/.kube/config
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 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 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 sigridjineth/kubespray-skills at c7de3c148c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c7de3c148c
- Manifest
- rke2-deployment/SKILL.md
- Scanned
- 1 file, 667 lines
About this skill
What it does
This skill automates deployments using Rancher Kubernetes Engine 2 (RKE2). It streamlines the process of setting up and configuring RKE2 clusters, handling tasks like node provisioning and cluster initialization. The skill aims to simplify complex infrastructure management for developers and operations teams.
When to use it
- Automating initial RKE2 cluster setup in a new environment.
- Reproducing consistent RKE2 deployments across multiple regions or cloud providers.
- Creating development environments with pre-configured RKE2 clusters.
- Deploying specific applications onto an existing RKE2 infrastructure.
Key capabilities
- RKE2 Cluster Initialization
- Node Provisioning
- Automated Configuration
Example prompts
- "Create a new RKE2 cluster with three nodes."
- "Configure the RKE2 cluster to use a specific Kubernetes version."
- "Deploy a sample application onto the existing RKE2 cluster."
Tips & gotchas
The skill requires familiarity with basic Kubernetes concepts. Ensure that necessary prerequisites, such as cloud provider credentials and network configurations, are in place before initiating deployments.