engine-manage

Manage the Kurtosis engine server across Docker and Kubernetes backends.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a unified toolkit to manage the Kurtosis engine server across Docker and Kubernetes backends, simplifying lifecycle operations and health checks for development and testing workloads.

Core Features & Use Cases

  • Start, stop, and restart the engine across both Docker and Kubernetes backends.
  • Check engine status, view version information, and monitor health.
  • View engine logs for troubleshooting and diagnostics.
  • Switch between Docker and Kubernetes backends and ensure gateway access for Kubernetes.
  • Use cases include recovering from engine startup failures, performing routine maintenance, and validating engine health in CI.

Quick Start

Start the engine with kurtosis engine start and verify it is running with kurtosis engine status.

Frequently Asked Questions about engine-manage

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

FAQPage Schema
How do I start the Kurtosis engine and check its status?

To start the Kurtosis engine, use the command `kurtosis engine start`, then verify it is running by executing `kurtosis engine status` to view its current health and version information.

Can I manage the Kurtosis engine server on a Kubernetes backend?

Yes, you can manage the Kurtosis engine server on Kubernetes by switching backends. You must ensure proper gateway access to perform lifecycle operations like starting, stopping, and viewing logs within the cluster.

What is the best way to troubleshoot Kurtosis engine startup failures?

The best way to troubleshoot Kurtosis engine startup failures is by viewing engine logs. Use the log viewing functionality to diagnose issues and perform a restart to recover the server across Docker or Kubernetes environments.

Does managing the Kurtosis engine require any special CLI tools or cluster access?

Yes, managing the Kurtosis engine requires the Kurtosis CLI and active cluster access. These prerequisites allow you to switch between Docker and Kubernetes backends and perform routine engine maintenance.

Why would I need to restart the Kurtosis engine server?

You need to restart the Kurtosis engine server to recover from startup failures or perform routine maintenance. Restarting helps validate engine health in CI and ensures stable operations across your Docker or Kubernetes environments.