k3s-ops

Deploy VibeTeam services to a k3s cluster using kustomize overlays.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/VibeTechnologies/VibeTeam --skill k3s-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k3s-ops
Source: https://github.com/VibeTechnologies/VibeTeam/tree/main/.opencode/skills/k3s-ops
Command: npx skills add https://github.com/VibeTechnologies/VibeTeam --skill k3s-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams deploy and manage VibeTeam services on a k3s cluster, automate worker scaling, and enforce consistent node naming to reduce manual ops toil.

Core Features & Use Cases

  • Deploy VibeTeam services to a k3s cluster using kustomize overlays for dev and prod environments.
  • Scale worker nodes via Terraform and VMSS or equivalent autoscaler configuration, with clear naming conventions for control-plane, standalone workers, and VMSS workers.
  • Enforce standardized node naming and lifecycle operations to simplify maintenance and auditing across environments.

Quick Start

Use the k3s-ops skill to deploy VibeTeam to a running cluster and apply auto-scaling.

Frequently Asked Questions about k3s-ops

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

FAQPage Schema
How do I automate k3s deployment and worker node scaling?

Automate k3s deployment and worker node scaling by using Terraform with VMSS or equivalent autoscaler configurations to provision and manage clusters, reducing manual operational toil across environments.

How does standardized node naming simplify k3s cluster maintenance?

Standardized node naming simplifies k3s cluster maintenance by enforcing consistent naming conventions for control-plane, standalone workers, and VMSS workers, which streamlines auditing and lifecycle operations across dev and prod environments.

Can I use kustomize overlays to deploy services to k3s for dev and prod?

Yes, you can deploy services to a k3s cluster using kustomize overlays to separate and manage configurations for dev and prod environments throughout the deployment lifecycle.

Do I need kubectl and Terraform to manage k3s autoscaling?

Yes, managing k3s autoscaling requires kubectl and Terraform to apply VMSS configurations, enforce node naming conventions, and execute ongoing scaling operations for worker nodes.

What is the best way to enforce node naming conventions across k3s environments?

The best way to enforce node naming conventions across k3s environments is to apply standardized naming rules for control-plane, standalone workers, and VMSS workers during initial deployment and ongoing scaling operations.