CNTRLPLANE-2202: add new exceptions + fail if uncaught default sa usage is detected

[ehearne-redhat]

This PR is a draft PR until we are certain no new default service account usage has been detected

This PR adds new exceptions previously not caught. It also ensures default service account usage test fail if uncaught exception is found, such as when a new deployment is added to a PR, which does not have an associated service account.

This should hopefully encourage service account usage to be thought of/enforce it when creating new deployments/daemonsets, etc.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@ehearne-redhat: This pull request references CNTRLPLANE-2202 which is a valid jira issue.

Details

In response to this:

This PR is a draft PR until we are certain no new default service account usage has been detected

This PR adds new exceptions previously not caught. It also ensures default service account usage test fail if uncaught exception is found, such as when a new deployment is added to a PR, which does not have an associated service account.

This should hopefully encourage service account usage to be thought of/enforce it when creating new deployments/daemonsets, etc.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ehearne-redhat
Once this PR has been reviewed and has the lgtm label, please assign stbenjam for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[ehearne-redhat]

/test all

[ehearne-redhat]

/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vpshere-ovn-upi

[ehearne-redhat]

/test e2e-vsphere-ovn-upi
/test e2e-gcp-ovn

[ehearne-redhat]

/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2

[ehearne-redhat]

/retest

[openshift-ci]

@ehearne-redhat: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-microshift-serial	8dc1218	link	true	/test e2e-aws-ovn-microshift-serial

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-trt]

Job Failure Risk Analysis for sha: 8dc1218

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial	IncompleteTests Tests for this run (23) are below the historical average (692): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)