-
Notifications
You must be signed in to change notification settings - Fork 693
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
Add e2e tests for multi-namespaces deployments #782
Comments
Some of the current assumptions in our test bootstrap code makes implementing this a bit tricky and more involved than I anticipated. I raised #1251 to discuss this further. |
Can you help me understand this use case? Why would we want them in separate namespaces? |
The use case would be to allow certain users (eg. a team in your org) to manipulate ES clusters, and let other users (eg. another team) tweak their Kibana settings with no access to the Elasticsearch namespace. |
I encountered a catch-22 situation while trying to write this test.
Due to these reasons, I have a test that works locally (operator is managing all namespaces) but it cannot be run in the CI environment (operator restricted to a single namespace). Rather than adding too many privileges to the CI environment, I am inclined to wait for a fix to #1438. |
Reopening this issue as multi-namespaces scenarios are still not run in our CI process. |
We have now this: cloud-on-k8s/test/e2e/kb/association_test.go Lines 24 to 40 in 459d005
Which makes me think we can close this issue. Please reopen if you had additional scenarios in mind. |
Use case:
Association should correctly be established between both.
So far our E2E tests do rely on a default
e2e
namespace for most tests.Here we need more plumbing to support multiple namespaces in the tests.
The text was updated successfully, but these errors were encountered: