feature: Manage created namespace's metadata
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the resource-sync path that creates namespaces and identify where namespace metadata could be supplied. Compare the requested behavior with Argo's managedNamespaceMetadata documentation and determine whether configuration belongs in controller options or the PublishedResource. Done means users can control labels and annotations on newly created namespaces, with coverage for the selected configuration path.
Written by the indexing model from the issue text.
Description
Feature Description
When syncing a resource to a variable namespace, syncagent ensures that the namespace gets created on the cluster. However there is no way to control e.g. labels/annotations that should be present on the new namespace.
Proposed Solution
Add a mechanism similar to Argo's managedNamespaceMetadata so users can control namespace metadata.
Alternative Solutions
The metadata could be set globally as a controller option for all created namespaces or dynamically in the publishedresource so the medata could differ between synced resources.
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kcp-dev/api-syncagent
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
kcp-dev/api-syncagent#163 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kcp-dev/api-syncagent#161 ·
-
kind/bug
kcp-dev/api-syncagent#182 · 1 comment · 1 assignee ·
-
bug: finalizer "syncagent.kcp.io/cleanup" on related resources block deletion of primary object Openkind/bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
kcp-dev/api-syncagent#172 · 1 comment · 1 reaction ·
-
kind/feature
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
kcp-dev/api-syncagent#157 ·
All issues in kcp-dev/api-syncagent
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100