[jcalloway_dev]

Really cool project. The self-development pipeline demo is what sold me — that's not just a toy, that's a proof of a real workflow pattern.

Few things I'm genuinely curious about:

On the CRD design — how are you handling secret/credential scoping per Task? Ephemeral pods are great for isolation, but if AgentConfigs can reference MCP servers, there's a credential surface area question worth thinking through early before people wire this into production pipelines.

On the container abstraction — does the standardized interface currently enforce any output schema validation, or is it mostly convention right now? Would love to know how strict that contract is in practice.

On adoption friction — K8s-native is powerful but raises the floor pretty high. Have you considered a lighter local mode (kind/minikube) with pre-baked configs to let people prototype workflows before committing to a full cluster setup?

Genuinely interested in where this goes. Watching the repo.

[gjkim042]

About handling secret/credential scoping, there’s todo issue to reference kubernetes secret from mcp config. https://github.com/axon-core/axon/issues/313

[gjkim042]

about the agent container interface,

It’s mostly about the inputs not the outputs. (How to inject prompts, context, skills…)

However, axon is trying to provide deterministic outputs such branch, PR link, etc, by executing a post script.

[gjkim042]

about the adoption friction, You can easily use it by kind create cluster + axon install.

Thanks for your interest. (Sorry for the late interaction, I thought the post was just abondoned.)