k8s-dev-deploy

Build, tag, push, and deploy Kurtosis dev images to a Kubernetes cluster.

547|97|Updated Feb 14, 2023
One-click install
npx skills add https://github.com/kurtosis-tech/kurtosis --skill k8s-dev-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-dev-deploy
Source: https://github.com/kurtosis-tech/kurtosis/tree/main/skills/k8s-dev-deploy
Command: npx skills add https://github.com/kurtosis-tech/kurtosis --skill k8s-dev-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build, push, and deploy Kurtosis dev images to a Kubernetes cluster for testing local changes, eliminating manual setup steps.

Core Features & Use Cases

  • Build multi-arch dev images for engine, core, and files-artifacts-expander and push them to Docker Hub with a unique tag.
  • Deploy or restart Kurtosis on a Kubernetes cluster to validate changes in a real dev environment.
  • Use Case: When iterating on code changes, quickly rebuild and deploy to a cluster to verify end-to-end behavior.

Quick Start

Build and push the Kurtosis dev images, then redeploy them to your Kubernetes cluster for testing changes.

Frequently Asked Questions about k8s-dev-deploy

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

FAQPage Schema
How do I build and push multi-arch dev images to Docker Hub for Kubernetes?

You can build and push multi-arch dev images to Docker Hub by automating the coordinated build, unique HEAD-based tagging, and push steps for engine, core, and files-artifacts-expander images.

What is the best way to deploy local code changes to a Kubernetes cluster for testing?

The best way to deploy local code changes to Kubernetes is to rebuild and push dev images, then automatically restart the engine in the cluster to validate end-to-end behavior.

Do I need Docker Hub to deploy multi-arch images to my Kubernetes cluster?

Docker Hub is required because the built multi-arch engine, core, and files-artifacts-expander dev images are tagged with a unique identifier and pushed to Docker Hub before restarting the engine in Kubernetes.

Does this workflow restart the Kubernetes engine when redeploying dev images?

The workflow restarts the Kurtosis engine in the Kubernetes cluster after building, tagging, and pushing the dev images to ensure the new changes are loaded and validated.

How does tagging work when building dev images for Kubernetes deployment?

Tagging works by applying a unique HEAD-based tag to the built engine, core, and files-artifacts-expander images, ensuring each deployment to the Kubernetes cluster tracks specific code iterations.