Skip to content
This repository was archived by the owner on Dec 3, 2024. It is now read-only.

Kustomize: Deployment namespaces should not be hardcoded #22

Closed
tparikh opened this issue Dec 10, 2020 · 1 comment
Closed

Kustomize: Deployment namespaces should not be hardcoded #22

tparikh opened this issue Dec 10, 2020 · 1 comment
Assignees
@NicolasT
Milestone
Demo 1

Comments

@tparikh
Copy link
Contributor

tparikh commented Dec 10, 2020

From container-object-storage-interface/cosi-controller-manager#9 (comment)

Generally, a kustomization should not deploy a namespace. It's up to the administrator to choose in which NS it gets deployed, and provision the NS.
This was referenced Dec 10, 2020
Closed
Merged
@wlan0 wlan0 added this to the Demo 1 milestone Dec 10, 2020
@NicolasT
Copy link
Contributor

/assign

@NicolasT NicolasT mentioned this issue Dec 17, 2020
Closed
shanduur pushed a commit to shanduur/container-object-storage-interface-api that referenced this issue Jun 6, 2024
@NicolasT
deploy: restore namespace handling in fullstack overlay
83f589a 
This patch removes hard-coded namespaces from the `base` layer, then
creates the `objectstorage-system` and `objectstorage-provisioner-ns`
Namespaces in the `fullstack` overlay, and uses them accordingly.

Closes: kubernetes-retired/container-object-storage-interface-controller#22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@NicolasT NicolasT

Labels
None yet
Projects
None yet
Milestone
Demo 1
Development

No branches or pull requests
3 participants
@NicolasT @wlan0 @tparikh