[anupamme]

Destructive Kubernetes operations including service deletion, endpoint collection deletion, and namespace deletion execute without structured audit logging. No record is created of who performed the action, when it occurred, or what resources were affected. This is defence-in-depth at cmd/delete.go:282 rather than a vulnerability I can show is exploitable here — it makes the failure mode explicit and bounded. Close it freely if the pattern is intentional.

Reference: CWE-778

What changed

• cmd/delete.go

Verification

No automated check could be run against this repository, so this change is unverified beyond review. Please treat it as a suggestion.

---

Automated security fix by OrbisAI Security

[baz-reviewer]

Baz Summary

Add structured audit messages to destructive Kubernetes cleanup operations, including service deletion, endpoint collection removal, and namespace deletion. Update deleteReleaseLeftovers and deleteNamespace to record the targeted resources before executing deletes.

Latest Contributors(0)

User	Commit	Date

  _{Activate to get a short verdict whether this PR is good to go or not}

  _{Activate Skill Maintainer to keep your skills up to date}

  _{This PR would have been improved with Baz Planner - Try it now}