Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COSI controller should have a recommended non-default namespace #95

Open
BlaineEXE opened this issue Aug 26, 2024 · 1 comment
Open
Assignees

Comments

@BlaineEXE
Copy link
Contributor

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
Copy link

I can work on it ?
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To do for v1alpha2
Development

No branches or pull requests

4 participants
@BlaineEXE @bouaouda-achraf and others