Closed gen1us2k closed 11 months ago
Attention: 476 lines
in your changes are missing coverage. Please review.
Comparison is base (
6e81abe
) 5.26% compared to head (93bd8b2
) 5.38%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
CHANGE DESCRIPTION
Problem: EVEREST-633
Enables multi-namespace support for the CLI
Solution details Multi-namespaces might be a challenge because of the difference between deploying operators. Everest deploys everest-operator with multi-namespace support and handles RBAC issues automatically while it deploys all other operators in the namespaced mode.
Another challenge is that during the provisioning the CLI creates OperatorGroup for the namespace to create service accounts with the proper permissions. Having an operator group with multiple values in
targetNamespaces
automatically makes every operator that is deployed to the namespace cluster-wide.We had a discussion about the
installation-namespace
andadditional-namespaces
ormanaged-namespaces
in the past and it looks like the hardcoding of percona-everest namespace for the everest-operator and everest-backend is the best way to provide a good UX for end users. Also, having--namespace
flag and changing it from string to string array adds multi namespace support and keeps backward compatibility.Since there's no way to get namespaces for the service account using standard tools the CLI creates a configmap with the configuration and once it's updated, the CLI restarts everest-operator and everest-backend when a new operator is added.
It misses monitoring changes but they will be added after merging backend changes to the main because it requires running a VM agent per namespace
CHECKLIST
Jira
Tests