feature: SyncAgent should remove stale Namespaces

Open
#113 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
backend, distributed-systems

Research direction

Start by tracing SyncAgent's namespace lifecycle and reproduce the reported MSP/KCP two-cluster scenario after deleting ordered resources and the workspace. Done means stale MSP namespaces are removed when the provider is deactivated or its workspace is deleted, with the resulting behavior verified in the relevant tests or reproduction.

Written by the indexing model from the issue text.

Description

kind/feature
Feature Description

Hi,

I am not sure if it is a feature that should already work or if the feature simply does not exist yet.
Please feel free to adjust this issue depending on what you do know, that I do not (yet).

Situation
Currently, I have two clusters running:

  • The MSP cluster: Contains operators and provides resources to the KCP cluster. The api-syncagent is deployed here.
  • The KCP cluster: Is connected to the MSP cluster and orders resources from it.

I have one operator running on the MSP cluster and I can successfully "order" resources from this operator from the KCP side.

Problem
Whenever I delete all ordered resources in KCP and also delete the workspace/account the namespace on MSP side still exists and does not get deleted.

Proposed Solution

The namespace on MSP side should be deleted either when the provider has been deactivated or at least when the workspace has been deleted.

Alternative Solutions

No response

Want to contribute?
  • I would like to work on this issue.
Additional Context

No response

Dominant language
Go
Stars
25
Forks
30
Avg merge
3d 9h
Merged PRs (30d)
2

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.

More from kcp-dev/api-syncagent

All issues in kcp-dev/api-syncagent

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.