COSI controller should have a recommended non-default namespace
Opened this issue · 1 comments
BlaineEXE commented
Bug Report
What happened:
Currently, the COSI deployment manifest installs the cosi controller in default
namespace. This is fine for a POC, but not for a stable project.
What you expected to happen:
COSI should have a recommended namespace for its controller install. Possibly objectstorage
to match objectstorage.k8s.io
domain.
How to reproduce this bug (as minimally and precisely as possible):
Anything else relevant for this bug report?:
Environment:
- Kubernetes version (use
kubectl version
), please list client and server: - Sidecar version (provide the release tag or commit hash):
- Provisoner name and version (provide the release tag or commit hash):
- Cloud provider or hardware configuration:
- OS (e.g:
cat /etc/os-release
): - Kernel (e.g.
uname -a
): - Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
bouaouda-achraf commented
I can work on it ?
/assign