Skip to content

Restrict direct apply to verified local k3d targets (#151) - #153

Merged
AntoineToussaint merged 2 commits into
mainfrom
issue-151-block-remote-direct-apply-verify-exact-local-k3d
Jul 28, 2026
Merged

Restrict direct apply to verified local k3d targets (#151)#153
AntoineToussaint merged 2 commits into
mainfrom
issue-151-block-remote-direct-apply-verify-exact-local-k3d

Conversation

@AntoineToussaint

@AntoineToussaint AntoineToussaint commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Closes #151.

Summary

  • Fail closed unless a direct deployment names an exact local k3d context whose complete cluster connection identity matches k3d ownership.
  • Make render-only behavior request-scoped and return every rendered service or module tree, its manifests, digest, and verified mutation target as evidence.
  • Preserve valid Kustomize image overrides while keeping pull, import, target revalidation, and apply failures fatal.

Test plan

  • go test ./...
  • go test -race ./pkg/deployments ./pkg/control ./pkg/orchestration ./cmd/deploy ./cmd/ci
  • go vet ./...
  • go run github.com/golangci/golangci-lint/cmd/golangci-lint@v1.64.8 run --new-from-rev=origin/main ./...

Risk

  • Direct apply now intentionally refuses local environments without an explicit cluster.context, or whose canonical kubeconfig connection settings differ from the k3d-owned cluster. Those deployments must declare the exact local target or use the render/GitOps path.

@AntoineToussaint
AntoineToussaint merged commit 5c67f26 into main Jul 28, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Block remote direct apply: verify exact local k3d target or require GitOps

1 participant