deploy-on-gvm

Deploy microservices to a GVM test instance via Jenkins builds.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mykaarma/claude-sutras --skill deploy-on-gvm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-on-gvm
Source: https://github.com/mykaarma/claude-sutras/tree/main/skills/deploy-on-gvm
Command: npx skills add https://github.com/mykaarma/claude-sutras --skill deploy-on-gvm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates deploying microservices to a GVM EC2 test instance using Jenkins, handling build triggering, status monitoring, and post‑deployment verification.

Core Features & Use Cases

  • Jenkins Build Triggering: Starts builds with optional branch selection.
  • Dynamic Service Type Detection: Determines whether the service runs on Kubernetes or Docker Compose by inspecting GVM configuration files.
  • Deployment Verification: Checks pod status in microk8s or container status in Docker, providing logs on failure.
  • Use Case: An engineer can quickly redeploy a changed service, confirm it’s running correctly, and avoid manual SSH and kubectl commands.

Quick Start

Ask the skill to deploy the specified service on the GVM, providing the service name and optional Git branch.

Frequently Asked Questions about deploy-on-gvm

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

FAQPage Schema
How do I trigger a Jenkins build to deploy a microservice to a GVM test instance?

You can deploy a microservice to a GVM test instance by triggering a Jenkins build with the service name and an optional Git branch. The deployment then proceeds automatically without requiring manual SSH commands.

How does Jenkins deployment verification work for Kubernetes and Docker Compose on a GVM?

Deployment verification works by checking pod status in microk8s or container status in Docker on the GVM. If the deployment fails, it automatically retrieves and provides the relevant logs for troubleshooting.

Do I need SSH access and Jenkins credentials to deploy services to a GVM?

Yes, deploying services to a GVM requires SSH access to the GVM EC2 instance and Jenkins credentials. These permissions are essential for triggering builds and verifying the resulting Kubernetes or Docker Compose deployment.

Can I dynamically detect if my service uses Kubernetes or Docker Compose when deploying to a GVM?

Yes, the deployment mechanism dynamically detects the service type by parsing service-mappings.yml and docker-compose.yml configuration files on the GVM. It determines whether to deploy using Kubernetes or Docker Compose based on these files.

What is the best way to redeploy a changed microservice to a GVM without manual kubectl commands?

The best way to redeploy a changed microservice without manual kubectl commands is to automate it through Jenkins. This triggers the build, monitors its status, and verifies the Kubernetes or Docker Compose deployment on the GVM automatically.

Why does my Jenkins deployment to a GVM test instance fail during pod or container verification?

Jenkins deployment to a GVM can fail during verification if the Kubernetes pods in microk8s or Docker containers do not reach a running state. The system provides failure logs to help diagnose the underlying build or deployment issue.