att-cloudnative-labs / att-cloudnative-labs/kubesweeper

Allow for *-based wildcard exclusion of namespaces

Open
#31 0 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue help wanted
Dominant language
Go
Stars
19
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Right now, excluded namespaces work with a 1-1 mapping. That is, if Kubernetes namespace `example-namespace` is in the excluded namespaces configuration, `example-namespace` is excluded from any kubesweeper deletion.

This issue would make it such that users can put `example-*` as an excluded namespace, which would exclude all namespaces that begin with `example-`.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named in the issue. Start by locating the excluded namespaces configuration and the filtering used before Kubernetes resources are deleted; trace how exact namespace matches are applied. Done means an exclusion such as example-* prevents deletion for every namespace beginning with example-, while exact exclusions continue to work.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.