cerc-io/stack-orchestrator
13
1
Fork 3
Code Issues 115 Pull Requests 23 Actions Packages Projects Releases 486 Wiki Activity

deployment stop destroys entire kind cluster even when shared by multiple deployments #979

New Issue
Open
opened 2026-01-24 17:56:00 +00:00 by AFDudley · 0 comments
AFDudley commented 2026-01-24 17:56:00 +00:00
Owner
Copy Link

Problem

When running laconic-so deployment stop for a k8s-kind deployment, it deletes the entire kind cluster instead of just stopping the pods for that specific deployment. This is destructive when multiple stacks share the same kind instance.

Steps to Reproduce

  1. Create two deployments targeting the same k8s-kind cluster (e.g., gorbagana-rpc and trashscan-explorer)
  2. Run laconic-so deployment --dir <first-deployment> stop
  3. The entire kind cluster is deleted, taking down ALL deployments

Expected Behavior

deployment stop should only remove the k8s resources (pods, services, configmaps) for that specific deployment, preserving the kind cluster and other deployments.

Actual Behavior

The command runs kind delete cluster which destroys the entire cluster.

Suggested Fix

Only delete clusters explicitly AND when there are no other deployments using it:

  • Track which deployments are using a shared kind cluster
  • Refuse to delete the cluster if other deployments are still active
  • Require an explicit flag (e.g., --delete-cluster) to force cluster deletion

Related

## Problem When running `laconic-so deployment stop` for a k8s-kind deployment, it deletes the entire kind cluster instead of just stopping the pods for that specific deployment. This is destructive when multiple stacks share the same kind instance. ## Steps to Reproduce 1. Create two deployments targeting the same k8s-kind cluster (e.g., gorbagana-rpc and trashscan-explorer) 2. Run `laconic-so deployment --dir <first-deployment> stop` 3. The entire kind cluster is deleted, taking down ALL deployments ## Expected Behavior `deployment stop` should only remove the k8s resources (pods, services, configmaps) for that specific deployment, preserving the kind cluster and other deployments. ## Actual Behavior The command runs `kind delete cluster` which destroys the entire cluster. ## Suggested Fix Only delete clusters explicitly AND when there are no other deployments using it: - Track which deployments are using a shared kind cluster - Refuse to delete the cluster if other deployments are still active - Require an explicit flag (e.g., `--delete-cluster`) to force cluster deletion ## Related - https://github.com/gorbagana-dev/gorbagana-rpc/issues/9
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
feature

   
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
in progress

   
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#979
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?