fix: isolate e2e commands to k3d cluster only - #19
Merged
Conversation
…l context All kubectl and helm calls now use a dedicated kubeconfig at ~/.k3d/kubeconfig-ownpulse-local.yaml instead of the default context. Commands other than 'up' refuse to run if the k3d cluster doesn't exist. This prevents accidental deployments to production when the default kubectl context points to a real cluster. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Critical safety fix:
opdev e2ecommands previously used the default kubectl context, meaning they could accidentally target production if that was the active context.Now:
~/.k3d/kubeconfig-ownpulse-local.yamlstatus,build,seedrefuse to run if the k3d cluster doesn't existupcreates the cluster and writes its own kubeconfigteardowndeletes both the cluster and its kubeconfigTest plan
go vet/go testpassopdev e2e statuswith no k3d cluster returns error: "not running — run 'opdev e2e up' first"opdev e2e --dry-runstill works (skips cluster check)🤖 Generated with Claude Code