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

Possibility to install operator into the same namespace as payloads it creates #239

Closed
afoninsky opened this issue May 7, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@afoninsky
Copy link

Currently, when I try to install operator into the same namespace using operatorhub - I receive an error:

OwnNamespace InstallModeType not supported, cannot configure to watch own namespace
# kubectl describe csv victoriametrics-operator.v0.14.1
...
  Install Modes:
    Supported:  false
    Type:       OwnNamespace
    Supported:  false
    Type:       SingleNamespace
    Supported:  false
    Type:       MultiNamespace
    Supported:  true
    Type:       AllNamespaces

Question: can we update install modes if there is no any technical restriction for doing it?

Refs:
https://gist.github.com/afoninsky/213f36581e22656bb6c7cda5ccfa2e5e
https://operator-framework.github.io/olm-book/docs/operator-scoping.html#targetnamespaces-and-their-realationship-to-installmodes

@f41gh7
Copy link
Collaborator

f41gh7 commented May 8, 2021

For now, there is technical restriction and operator supports only cluster wide install.

I think, its possible to support single namespace installation mode, but its a bit complicated.

@f41gh7
Copy link
Collaborator

f41gh7 commented Sep 27, 2021

Added to the v0.19.0 release.

@f41gh7 f41gh7 closed this as completed Sep 27, 2021
@ctml91
Copy link

ctml91 commented Jan 9, 2022

@f41gh7 Where is this configured? I've installed v0.21.0 from OperatorHub in OpenShift and the only option provided is "all namespaces" and the CSV looks like below. I'm not too sure how to use WATCH_NAMESPACE with an OLM install?

My goal is to deploy VM without users/tenants from other namespaces being able to access cluster level resources & metrics (e.g. by deploying their own VM instance, I am not sure if they are still restricted due to RBAC of the VM deployments in their namespace or the operator running globally from my namespace is going to allow them to do that kind of thing). Also if I use same namespace deploy is it still possible to scrape metrics from services in other namespaces?

Thanks in advance!

  installModes:
    - supported: false
      type: OwnNamespace
    - supported: false
      type: SingleNamespace
    - supported: false
      type: MultiNamespace
    - supported: true
      type: AllNamespaces

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants