Skip to content

Kamaji blocking namespace removing #1660

New issue
New issue
Closed
Closed
Kamaji blocking namespace removing#1660
Labels
kind/bugCategorizes issue or PR as related to a bug

Description

@kvaps
Andrei Kvapil (kvaps)
opened on Nov 26, 2025

we need to execute following:

kubectl patch secret -n tenant-tenantsm -p '{"metadata":{"finalizers":null}}' --type=merge kubernetes-two-datastore-config
kubectl patch tenantcontrolplanes.kamaji.clastix.io -n tenant-tenantsm -p '{"metadata":{"finalizers":null}}' --type=merge kubernetes-two

to remove finalizers

Activity

  1. Andrei Kvapil (kvaps)
    added
    kind/bugCategorizes issue or PR as related to a bug
    on Nov 26, 2025

  2. dosubot commented on Feb 25, 2026

    @dosubot
    dosubotBot
    on Feb 25, 2026 – with DosuBot

    Hi, Andrei Kvapil (@kvaps). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You requested a feature in Kamaji to automate unblocking namespace removal by patching resources to remove finalizers.
    • You provided example kubectl commands for clearing finalizers on secrets and tenant control plane resources.
    • This feature would add built-in support in Kamaji to handle finalizer removal and streamline cleanup processes.
    • There has been no further activity or comments on this issue since it was opened.

    Next Steps:

    • Please let me know if this feature request is still relevant to the latest version of Kamaji by commenting on this issue.
    • If I do not hear back within 7 days, I will automatically close this issue.

    Thank you for your understanding and contribution!

  3. dosubot
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Feb 25, 2026

  4. kvaps commented on Feb 25, 2026

    @kvaps
    Andrei Kvapil (kvaps)
    on Feb 25, 2026
    MemberAuthor

    Should be fixed already

  5. Andrei Kvapil (kvaps)
    closed this as completedon Feb 25, 2026

  6. dosubot commented on Feb 25, 2026

    @dosubot
    dosubotBot
    on Feb 25, 2026 – with DosuBot

    Thank you for your help in resolving this issue, Andrei Kvapil (@kvaps)! We appreciate your contribution.

  7. dosubot
    removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions