pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for KSail

Pod holds 11 of 11 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to KSail.

Most discussed

CI DoctorDaily Plan Detection Step Failure - Silent Copilot CLI Exit Code 1

Summary

The Daily Plan workflow failed in the detection job with a silent Copilot CLI failure. The agent job completed successfully and produced outputs, but the subsequent threat detection step failed immediately with exit code 1 without producing any diagnostic output.

Failure Details

Read the thread · 2026-02-26 · closed · outside contributor · 1 comment

Daily Refactor - Decompose Talos Hetzner detachISOsAndReboot function

Goal and Rationale

Goal: Decompose the detachISOsAndReboot function in the Talos Hetzner provisioner from 86 lines to focused, single-responsibility helpers.

Why This Matters:

  • Long functions (>70 lines) are harder to understand, test, and maintain
  • The function had three distinct responsibilities mixed together
  • Each phase deserves its own focused function with clear naming

Approach

Extracted the 86-line detachISOsAndReboot function into 4 focused helpers:

  1. **`logIns

Read the thread · 2026-02-18 · closed · outside contributor · 0 comments

[agentics] Update Docs failed

Workflow Failure

Workflow: Update Docs
Branch: main
Run URL: https://github.com/devantler-tech/ksail/actions/runs/22117910498

⚠️ No Safe Outputs Generated: The agent job succeeded but did not produce any safe outputs. This typically indicates:

  • The safe output server failed to run
  • The prompt failed to generate any meaningful result
  • The agent should have

Read the thread · 2026-02-17 · closed · outside contributor · 1 comment

[agentics] CI Failure Doctor failed

Workflow Failure

Workflow: CI Failure Doctor
Branch: main
Run URL: https://github.com/devantler-tech/ksail/actions/runs/21511822612

Action Required

Debug this workflow failure using the agentic-workflows agent:

/agent agentic-workflows

When prompted, instruct the agent to debug this workflow failure.

Generated from [CI Failure Doctor](https:/

Read the thread · 2026-01-30 · closed · outside contributor · 2 comments

[bug]: Failed to validate tool mcp_devantler-tec_ksail_cluster_read: Error: tool parameters array type must have items. Please open an issue for the MCP server or extension which provides this tool

Expected Behavior

MCP Server should work

Actual Behavior

MCP Server does not work

Steps to Replicate

Try to add the MCP Server to VSCode, and notice that it fails during validation when you send off a prompt:

"github-agentic-workflows": {
  "command": "gh",
  "args": [
    "aw",
    "mcp-server"
  ],
},

Read the thread · 2026-01-29 · closed · outside contributor · 2 comments

[feature]: Add MCP Server

User Story

As a user, I want to interact with Kubernetes via the MCP, So that I can use KSail from my chosen AI Assistant.

Acceptance Criteria

  • Criteria 1: Implement a MCP server for KSail using https://github.com/modelcontextprotocol/go-sdk
  • Criteria 2: Auto discover all cobra commands and make them available as MCP tools (similar to how ksail chat discovers and provides tools)

Read the thread · 2026-01-27 · closed · outside contributor · 1 comment

[feature]: Add permission-gating of all mutable operations or tool calls made with ksail chat

User Story

As a user, I want ksail chat to prompt me to allow (y) or disallow (n) a mutable operation or tool call before it is fired, So that the AI Assistant operates safely, and does not break things by mistake.

Acceptance Criteria

  • Criteria 1: ksail chat prompts the user to allow (y) or disallow (n) any mutable operation or tool call.
  • Criteria 2: ksail chat auto-allows non-mutable operations or tool calls.
  • Criteria 3: The prompt is nicely presen

Read the thread · 2026-01-26 · closed · outside contributor · 1 comment

Test check command to ensure it fails if a kustomization is not succesfull

Description

No response

Read the thread · 2024-01-11 · closed · outside contributor · 0 comments

Most recent

Upgrade workflows to gh-aw v0.45.0

Overview

This PR upgrades all agentic workflows from gh-aw v0.44.0 to v0.45.0. All 17 workflows compiled successfully with 0 errors.

Changes Summary

Version Updates

  • gh-aw: v0.44.0 → v0.45.0
  • Setup action: github/gh-aw/actions/setup@v0.44.0 → @v0.45.0
  • Agent descriptor: Updated all v0.44.0 references to v0.45.0

Files Modified

  • .github/agents/agentic-workflows.agent.md - Updated version references
  • .github/workflows/agentics-maintenance.yml - Version and

Read the thread · 2026-02-16 · closed · outside contributor · 0 comments

chore(workflows): upgrade to gh-aw v0.44.0

Summary

This PR upgrades all agentic workflows to the latest version of gh-aw (v0.44.0).

Changes Applied

Automatic Codemods

Ran gh aw fix --write which applied the following fixes:

  • Removed deprecated discussion: true field from add-comment safe-output configuration in .github/workflows/daily-backlog-burner.md

This field was deprecated as the add_comment handler now auto-detects the target type (issue, PR, or discussion) or accepts a discussion_number parameter.

Read the thread · 2026-02-15 · closed · outside contributor · 0 comments

[chore]: Add Daily Test Coverage Improver agentic workflow

User Story

As a maintainer, I want to add the Daily Test Coverage Improver agentic workflow, So that test coverage is automatically improved by adding tests to under-tested areas of the codebase.

Acceptance Criteria

  • Install gh aw extension (gh extension install githubnext/gh-aw)
  • Add daily-test-improver workflow via PR (gh aw add githubnext/agentics/daily-test-improver --pr)
  • Configure coding agent and add API key secret to the repository
  • Enable "

Read the thread · 2026-01-06 · closed · outside contributor · 0 comments

The remaining reports are on the project's issue tracker.