kubesphere / kubesphere/ks-devops

Request to support share ConfigMap, Secret, etc. to different namespace

Open
#554 0 comments 0 reactions 0 assignees View on GitHub
kind/feature
Dominant language
Go
Stars
164
Forks
140
PR merge metrics
No merged PRs in 30d

Description

### What is version of KubeSphere DevOps has the issue?

none

### How did you install the Kubernetes? Or what is the Kubernetes distribution?

_No response_

### Describe this feature

Some potential projects are able to copy (with or without modification) to other namespaces. Such as:

* https://github.com/kyverno/kyverno

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue names no ks-devops file, test, or entry point. Start by reviewing the linked Kyverno project, then determine which resources and namespace-copy behavior are in scope. Done should mean the supported ConfigMap, Secret, or other resources can be copied to another namespace with the required modification behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.