kubesphere / kubesphere/ks-devops
The actual namespace of the deployment in "Continuous Deployments" is not the same as the configured "deployment location"
Nobody has claimed this yet.
- 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?
v3.3.0-rc.2
How did you install the Kubernetes? Or what is the Kubernetes distribution?
No response
What happened?
First, I set up the deployment location which is named pro.
But this deployment was deployed into osf2f-system, and the pro was also created.
I don't know if it is because there is a namespace value osf2f-system in the kustomization.yaml, maybe it should need to override that.
A more serious situation is if I create 2 "Continuous Deployments" which both set up the same namespace value in the kustomization.yaml as the above, they will be deployed into one namespace even though I set a different "deployment location".
They were all deployed to osf2f-system.
Relevant log output
No response
Additional information
No response
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.
Research direction
Reproduce the deployment using two Continuous Deployments with different deployment locations and the same namespace in kustomization.yaml. Trace how the configured deployment location and kustomization.yaml namespace are consumed, then verify that each deployment is created in its selected namespace without merging into the configured namespace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, yaml
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100