search

IBM / operand-deployment-lifecycle-manager

Managing the lifecycle for a group of operands
Apache License 2.0
32 stars 46 forks source link

Remove ClusterPermission: Check namespace before creating it for managed operators #532

Closed horis233 closed 3 years ago

horis233 commented 4 years ago

/kind feature

ODLM can manage any operator in any namespace. In one namespace mode, the dedicated namespace already exists, so we can enhance to check if check the manged operator is deployed in the same namespace as the ODLM. If it is, then skip the check.

Describe the solution you'd like [A clear and concise description of what you want to happen.]

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

chenzhiwei commented 4 years ago

WATCH_NAMESPACE will be a comma separated string, such as namespace1,namespace2,namespace3.

  1. if WATCH_NAMESPACE is blank string(“”), the ODLM is in all namespace mode, so create the managed operator namespace
    1. if the managed operator namespace is in WATCH_NAMESPACE, skip creating
    2. if the managed operator namespace is not in WATCH_NAMESPACE, throw no permission or error configuration message