Repository navigation
Releases
v0.6.0
What's New in v0.6.0
Plugin System
- Plugin marketplace — Browse and install plugins from http://market.deckwatch.io directly within Settings → Plugins
- Application-level plugin association — Associate plugins with applications; reconciler applies them source-agnostically (kubectl, ArgoCD, MCP all work)
- Plugin config schema — Plugins declare their own configuration fields; dynamic settings UI renders automatically
- Provisioned resources — Infrastructure tab (RDS, S3, sidecars) via
provision()/deprovision()exports; state injected into all deployments/cronjobs - Sidecar injection — Plugins return
sidecars: Vec<SidecarSpec>fromprovision(); reconciler patchesspec.template.spec.containersvia SSA - Deployment annotations — Provisioned resources stamp
deckwatch.io/*annotations on deployments - Deprovision lifecycle — Final RDS snapshot before deletion; S3 retains with operator guidance
Developer Experience
- WASM upload endpoint —
POST /api/plugins/{name}/uploadfor local dev; instant reload without GitHub push - Plugin error logging —
result.errorssurfaces plugin failures through deckwatch's tracing subscriber
ServiceAccount CRUD
- Full SA management via REST API, MCP tools, and UI
Fixes
- ServiceAccounts ClusterRole permission
- Plugin reconciler migration conflict resolved
now()host function for accurate WASM clock (no more epoch timestamps)
v0.5.8
What's Changed
- fix: bump plugin
apply()tracing fromdebug!toinfo!— plugin calling/completed events now visible at the default log level without anyRUST_LOGchanges
v0.5.4 — MCP tuning, plugin networking, directory cleanup
What's new
MCP resource-scoped org hints
Define per-group guidance in Settings → MCP Tuning. Deckwatch appends your hint to tool descriptions only when that resource group is in scope — namespace guidance fires for namespace tools, deployment guidance for deployment tools, etc. No more global instructions polluting unrelated interactions.
Also adds global instructions injected via the MCP initialize response for cross-cutting guidance.
Plugin: inherit_env_keys
Credentials mounted as Kubernetes Secret env vars on the deckwatch pod can now be passed to plugins without storing them in settings. Deckwatch reads the named env vars from the process environment at invocation time and injects them into the plugin's extism config — overriding any same-named static config entry so rotated credentials always win.
{ "inherit_env_keys": ["AWS_ACCESS_KEY_ID", "AWS_SECRET_ACCESS_KEY", "AWS_SESSION_TOKEN"] }MCP prompt improvements
pre-deployment-check: explicitly states no CI pipeline is needed — deckwatch GitOps IS the build pipeline. All 10 checklist items reframed accordingly.deployment-readiness-check: replaced:latesttag check with GitOps build status and OOMKilled detection.
Repository cleanup
- Removed stale
Making an AI app.mdfrom root - Moved 21 handler test files from
src/root intosrc/handlers/alongside their modules (structural cleanup, no behaviour change) - Updated all
#[path]annotations
Documentation
SETTINGS.md:inherit_env_keysandmcp_tuningfully documented with examplesMCP.md: new MCP Tuning sectionPLUGINS.md: full plugin config schema, roadmap updated
Companion repos
- deckwatch-plugin-sdk v0.4.0 —
PluginMetadata,plugin_outputs,outputs - deckwatch-plugin-aws v0.1.0 — unified IAM + RDS + S3 + AWS Backup
v0.5.3 — Plugin dependency resolution & unified AWS plugin
What's new
Plugin dependency resolution
Plugins now declare capabilities via a metadata() WASM export. Deckwatch automatically topologically sorts them at load time — operators never need to worry about plugin ordering.
PluginMetadatawithprovides,depends_on,optional_depends_oncapability IDs- Topological sort (Kahn's algorithm) before any
apply()calls - Output threading: each plugin's
PluginResult.outputsis passed to subsequent plugins asPluginContext.plugin_outputs
Cloud-agnostic plugin networking
allowed_hostsper plugin — controls which URLs the plugin can reach via extism's HTTP host functionconfigmap per plugin — operator-supplied key-value pairs (credentials, endpoints) injected into extism config; deckwatch has zero cloud-specific knowledge
Plugin settings UI
Settings → Plugins now shows per-plugin allowed_hosts and config key-value editor (values containing "secret", "password", or "token" are auto-masked).
Also in this release
- Ingress host chips are clickable links
service_account_namebinding in PluginResult- Labels, annotations, and node affinity management in the deployment UI
update_deployment_labels,update_deployment_annotations,update_deployment_affinityMCP tools
Companion SDK
deckwatch-plugin-sdk v0.4.0 — PluginMetadata, plugin_outputs, outputs
AWS plugin
deckwatch-plugin-aws — unified IAM + RDS + S3 provisioning with AWS Backup snapshots, automatic dependency ordering
v0.5.2 — MCP metrics and Grafana dashboards
What's new
MCP observability
deckwatch_mcp_requests_total{method,status}+ duration histogram on every JSON-RPC call through/mcpdeckwatch_mcp_tool_calls_total{tool,status}+ duration histogram for deckwatch-native tools (create_application, set_gitops, trigger_build, plugins, monitoring, etc.)- K8s-passthrough tools are self-instrumented by the mcp-k8s library via
mcp_k8s_tool_calls_total— no double-counting
Grafana dashboards
Two pre-built dashboards added under dashboards/:
- Deckwatch Overview — HTTP traffic, GitOps pipeline, k8s API, frontend RUM (Core Web Vitals), and an AI/MCP activity row
- Deckwatch MCP — deep-dive MCP dashboard with per-method request rates, per-tool call rates, deckwatch-native vs k8s source split, p95/p99 latency, permission denials, and error breakdown
Dependency updates
v0.5.1 — CI and build fixes
Patch release fixing the v0.5.0 container image build and CI pipeline after adding the extism/wasmtime dependency.
Fixes
- Dockerfile: bump Rust from 1.89 → 1.91 — required by extism's wasmtime/cranelift dependencies
- CI: bump toolchain from 1.89 → 1.91 for the same reason
- Cargo.lock: refresh after mcp-k8s git dependency drifted (was breaking
cargo check --locked) - Clippy: resolve
field_reassign_with_defaultwarnings in plugin refresh spawns - rustfmt: apply formatting to new plugin code
What's in v0.5.x
See the v0.5.0 release notes for the full feature list — external WASM plugin system, MCP plugin tooling, and MCP tool naming standardisation.
v0.4.16
Fix registry manifest Content-Type detection — multi-arch image pulls now work correctly.
v0.4.15
MCP Prompts + Crane Manifest Fix
New: MCP Prompts
pre-deployment-check— reviews the local codebase for deckwatch readiness (Dockerfile, git repo, health endpoints, database config, secrets, dependencies)deployment-readiness-check— checks a deployed application's health using MCP tools (pods, gitops, ingress, probes, resource limits)
Fix: Crane Manifest Assembly
- Added
--docker-empty-baseto match Kaniko's Docker V2 manifest format - Added
--flattento handle stale nested indexes from partial builds
v0.4.14
Propagate build-group labels to pod templates so build logs appear in the UI.
v0.4.13
Fixes
- Manifest assembly: Removed
--docker-media-typescrane flag (removed in recent crane versions) - Label reconciliation: Watcher ensures
deckwatch.io/applicationlabel persists on deployments after builds - Stable encryption key: Helm chart supports
encryptionKey.valueto prevent ArgoCD from regenerating the key on sync - Settings UI: Git token updates via Settings page no longer silently fail