zalando-incubator / zalando-incubator/stackset-controller

Prevent deletion of Stacks still getting traffic.

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
183
Forks
29
Avg merge
3d 18h
Merged PRs (30d)
5

Description

Currently, if you delete an application stack $ kubectl delete stack <stack-name> Kubernetes will automatically clean up all dependent resources including the Deployment and Service resources.

The resource could be "protected" with a Finalizer so the controller can halt deleting if the stack is still getting traffic. If this happens it should issue events about it (#12).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Stack controller's deletion handling and the code that determines whether a Stack is still receiving traffic. Review Kubernetes finalizers and issue #12's event requirement. Done means deletion is halted while traffic remains, dependent resources are protected, and the controller emits the specified events.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.