skills.rest
omnistrate-community
omnistrate-communityOFFICIAL
Explore all skills by this author →
Website𝕏@omnistrateGitHub

Debugging Omnistrate Deployments

Guide operators through a two-phase workflow to debug Omnistrate deployment failures.

1|2|Updated Nov 10, 2025
Search Tags:#workflow#debugging#helm#kubectl#deployments#Omnistrate
One-click install
npx skills add https://github.com/omnistrate-community/kubecon-2025-agent-template --skill debugging-omnistrate-deployments
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Debugging Omnistrate Deployments
Source: https://github.com/omnistrate-community/kubecon-2025-agent-template/tree/main/.claude/skills/omnistrate-sre
Command: npx skills add https://github.com/omnistrate-community/kubecon-2025-agent-template --skill debugging-omnistrate-deployments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides operators through a structured debugging workflow to identify root causes of Omnistrate deployment failures and noisy statuses while minimizing token usage.

Core Features & Use Cases

  • Progressive two-phase workflow: Phase 1 gathers deployment status and related workflows; Phase 2 analyzes workflow events with targeted detail as needed.
  • Application-level debugging assistance: When deployments are DEPLOYING with probe failures, the skill guides steps to collect logs, inspect resources, and isolate issues.
  • Helm verification and broader context: Includes steps to verify Helm releases and optionally pull broader event data to triangulate root causes.
  • Real-world scenarios: Use for failed deployments, unhealthy pods, startup probes failing, and unclear Helm states.

Quick Start

  • Run the deployment status: omctl instance describe <instance-id> --deployment-status --output json
  • List related workflows: omctl workflow list --service-id <id> --environment-id <id> --output json
  • Inspect workflow events: omctl workflow events <workflow-id> --service-id <id> --environment-id <id> --output json
  • If a resource needs detail: omctl workflow events <workflow-id> --service-id <id> --environment-id <id> --resource-key <name> --step-types Deployment --detail --output json
  • For application-level debugging: omctl deployment-cell update-kubeconfig <cell-id> --kubeconfig /tmp/kubeconfig kubectl logs <pod-name> -n <instance-id> --kubeconfig /tmp/kubeconfig --tail=50

Frequently Asked Questions about Debugging Omnistrate Deployments

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

FAQPage Schema
How do I debug Omnistrate deployments stuck in DEPLOYING or FAILED status?▼

Debug Omnistrate deployments by running a progressive two-phase workflow that gathers deployment status and workflow events to identify root causes. Phase 1 collects status via omctl instance describe, and Phase 2 inspects related workflow events to isolate failures.

Why are startup probes failing in my Omnistrate deployment and how do I check logs?▼

Startup probe failures require application-level debugging using kubectl logs to inspect pod behavior. Update your kubeconfig with omctl deployment-cell update-kubeconfig, then run kubectl logs on the failing pod to isolate the application issue.

What is the best way to verify Helm release states for failed Omnistrate instances?▼

Verifying Helm releases for Omnistrate instances involves checking workflow events and optionally pulling broader event data to triangulate root causes. The progressive workflow includes specific steps to clarify ambiguous Helm release states during deployment failures.

How do I inspect specific resource events for an Omnistrate workflow?▼

Inspect specific Omnistrate resource events by running omctl workflow events with the resource-key and step-types Deployment flags. Adding the --detail flag provides targeted event data for the specified resource, minimizing unnecessary token usage.

Does the Omnistrate debugging workflow work across both development and production environments?▼

The Omnistrate debugging workflow applies to instance deployments across both development and production environments. It handles FAILED or DEPLOYING statuses by using token-conscious reporting to minimize data usage while identifying root causes in any environment.

Related Skills

Explore More Software Engineering Skills→
hanamizukihanamizuki
127

asc-id-resolver

Map App Store Connect names to IDs for asc CLI commands.

Community
Intermediate
omnistrate-ossomnistrate-oss

Debugging Omnistrate Deployments

Diagnose Omnistrate deployment failures with a two-phase JSON workflow.

Official
Advanced
phuetzphuetz
30

kubernetes

Consolidate kubectl, Helm, and ArgoCD workflows for Kubernetes cluster administration.

Community
Advanced
huynguyenhhuynguyenh
3

hnh-k8s

Run kubectl commands to debug and monitor Kubernetes EKS clusters.

Community
Intermediate