search

kubernetes-sigs / container-object-storage-interface-controller

Container Object Storage Interface (COSI) controller responsible to manage lifecycle of COSI objects.
Apache License 2.0
93 stars 28 forks source link

05/04/24 - Single namespace installation #120

Closed Zvezdoreel closed 1 month ago

Zvezdoreel commented 7 months ago

Enhancement

Is your feature request related to a problem?/Why is this needed I want to deploy multiple instances of this controller in different namespaces

Describe the solution you'd like in detail per namespace installation, Id like the controller to watch resources in the namespace it installed in

Describe alternatives you've considered maybe a list of allowed namespaces

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

niranjandarshann commented 3 months ago

@Zvezdoreel Thank you For your contribution. I find this as required one too as Implementing per-namespace installation so that each controller instance is limited to watching resources in its own namespace. This simplifies management and ensures better isolation between different namespaces.

It is useful for better isolation between different namespaces.

niranjandarshann commented 3 months ago

@Zvezdoreel I was looking for the alternative way to achieve it and here what i understood is that we can achieve it by: Deploying a controller in each namespace, configuring each instance to watch only its namespace using the WATCH_NAMESPACE environment variable. This ensures isolation and simple management. Alternatively, deploy a cluster-wide controller with namespace filtering logic and use Kubernetes RBAC to restrict its permissions. This approach balances isolation with resource efficiency.

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/container-object-storage-interface-controller/issues/120#issuecomment-2363037087): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.