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

Move user defined service account e2e to one namespace per spec #2717

Conversation

perdasilva
Copy link
Collaborator

@perdasilva perdasilva commented Mar 27, 2022

Signed-off-by: perdasilva [email protected]

Description of the change:
This PR moves the service account e2e to one namespace per spec it also adds options to the test namespace creation to support different operator groups in a more friendly way

NOTE: Probably better to merge this one last and update all the other e2e tests on the rebase?

Motivation for the change:
CI stability

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky
  • Tests that remove the [FLAKE] tag are no longer flaky

@openshift-ci openshift-ci bot requested review from anik120 and kevinrizza March 27, 2022 10:31
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 27, 2022
@perdasilva perdasilva force-pushed the refactor_user_defined_e2e branch 8 times, most recently from 0701465 to 5622d43 Compare March 30, 2022 15:27
@perdasilva perdasilva force-pushed the refactor_user_defined_e2e branch from 5622d43 to 11535dc Compare March 30, 2022 16:00
Copy link
Member

@timflannagan timflannagan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code changes lgtm and I pulled this down locally and ran the user-defined SA suite in isolation five times and all runs ended up passing. I didn't notice any namespace-level leakage which is nice, but there's a good chunk of cluster-scoped leakage that doesn't appear to effect the test cases themsevles:

$ k get crds --sort-by '.metadata.creationTimestamp'
...
insfw7fx.cluster.com                          2022-03-30T15:31:48Z
inskksxb.cluster.com                          2022-03-30T15:33:18Z
insrhw6v.cluster.com                          2022-03-30T15:40:27Z
inshwndx.cluster.com                          2022-03-30T15:41:57Z
ins6s2vn.cluster.com                          2022-03-30T15:43:52Z
insxch24.cluster.com                          2022-03-30T15:45:22Z
inskztgv.cluster.com                          2022-03-30T15:49:49Z
insqzzmd.cluster.com                          2022-03-30T15:51:17Z
insgj5fk.cluster.com                          2022-03-30T15:53:39Z
insrfk9j.cluster.com                          2022-03-30T15:55:09Z
insh482m.cluster.com                          2022-03-30T15:57:17Z
insv4lqb.cluster.com                          2022-03-30T15:58:44Z
$ k get clusterroles --sort-by '.metadata.creationTimestamp'
...
insfw7fx.cluster.com-v1alpha1-admin                                    2022-03-30T15:31:52Z
insfw7fx.cluster.com-v1alpha1-view                                     2022-03-30T15:31:52Z
insfw7fx.cluster.com-v1alpha1-edit                                     2022-03-30T15:31:52Z
insfw7fx.cluster.com-v1alpha1-crdview                                  2022-03-30T15:31:52Z
inskksxb.cluster.com-v1alpha1-crdview                                  2022-03-30T15:33:23Z
inskksxb.cluster.com-v1alpha1-admin                                    2022-03-30T15:33:23Z
inskksxb.cluster.com-v1alpha1-edit                                     2022-03-30T15:33:23Z
inskksxb.cluster.com-v1alpha1-view                                     2022-03-30T15:33:23Z
insrhw6v.cluster.com-v1alpha1-view                                     2022-03-30T15:40:32Z
insrhw6v.cluster.com-v1alpha1-admin                                    2022-03-30T15:40:32Z
insrhw6v.cluster.com-v1alpha1-crdview                                  2022-03-30T15:40:32Z
insrhw6v.cluster.com-v1alpha1-edit                                     2022-03-30T15:40:32Z
inshwndx.cluster.com-v1alpha1-view                                     2022-03-30T15:42:02Z
inshwndx.cluster.com-v1alpha1-admin                                    2022-03-30T15:42:02Z
inshwndx.cluster.com-v1alpha1-edit                                     2022-03-30T15:42:02Z
inshwndx.cluster.com-v1alpha1-crdview                                  2022-03-30T15:42:02Z
ins6s2vn.cluster.com-v1alpha1-admin                                    2022-03-30T15:43:57Z
ins6s2vn.cluster.com-v1alpha1-crdview                                  2022-03-30T15:43:58Z
ins6s2vn.cluster.com-v1alpha1-edit                                     2022-03-30T15:43:58Z
ins6s2vn.cluster.com-v1alpha1-view                                     2022-03-30T15:43:58Z
insxch24.cluster.com-v1alpha1-admin                                    2022-03-30T15:45:27Z
insxch24.cluster.com-v1alpha1-edit                                     2022-03-30T15:45:27Z
insxch24.cluster.com-v1alpha1-crdview                                  2022-03-30T15:45:27Z
insxch24.cluster.com-v1alpha1-view                                     2022-03-30T15:45:27Z
inskztgv.cluster.com-v1alpha1-crdview                                  2022-03-30T15:49:54Z
inskztgv.cluster.com-v1alpha1-edit                                     2022-03-30T15:49:54Z
inskztgv.cluster.com-v1alpha1-view                                     2022-03-30T15:49:54Z
inskztgv.cluster.com-v1alpha1-admin                                    2022-03-30T15:49:54Z
insgj5fk.cluster.com-v1alpha1-edit                                     2022-03-30T15:53:44Z
insgj5fk.cluster.com-v1alpha1-crdview                                  2022-03-30T15:53:44Z
insgj5fk.cluster.com-v1alpha1-view                                     2022-03-30T15:53:44Z
insgj5fk.cluster.com-v1alpha1-admin                                    2022-03-30T15:53:44Z
insrfk9j.cluster.com-v1alpha1-edit                                     2022-03-30T15:55:13Z
insrfk9j.cluster.com-v1alpha1-view                                     2022-03-30T15:55:13Z
insrfk9j.cluster.com-v1alpha1-admin                                    2022-03-30T15:55:13Z
insrfk9j.cluster.com-v1alpha1-crdview                                  2022-03-30T15:55:13Z
insh482m.cluster.com-v1alpha1-edit                                     2022-03-30T15:57:24Z
insh482m.cluster.com-v1alpha1-admin                                    2022-03-30T15:57:24Z
insh482m.cluster.com-v1alpha1-crdview                                  2022-03-30T15:57:24Z
insh482m.cluster.com-v1alpha1-view                                     2022-03-30T15:57:24Z
insv4lqb.cluster.com-v1alpha1-admin                                    2022-03-30T15:58:48Z
insv4lqb.cluster.com-v1alpha1-edit                                     2022-03-30T15:58:48Z
insv4lqb.cluster.com-v1alpha1-view                                     2022-03-30T15:58:49Z
insv4lqb.cluster.com-v1alpha1-crdview                                  2022-03-30T15:58:49Z

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 30, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva, timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [perdasilva,timflannagan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit d6346a1 into operator-framework:master Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants