Repository: kubernetes-sigs/security-profiles-operator
Pull request #991 (2022-06-13 15:15:34)

Create baseprofiles in CI


#### What type of PR is this?


/kind feature


#### What this PR does / why we need it:
Creating the baseprofiles in the CI.
#### Which issue(s) this PR fixes:

<!--
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.

Fixes #

or

None
-->
None
#### Does this PR have test?
None
<!--
If tests aren't applicable just write N/A.
-->

#### Special notes for your reviewer:
None
#### Does this PR introduce a user-facing change?

<!--
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".

For more information on release notes see: https://git.k8s.io/community/contributors/guide/release-notes.md
-->

```release-note
None
```


k8s-ci-robot: [APPROVALNOTIFIER] This PR is **APPROVED**

This pull-request has been approved by: *<a href="https://github.com/kubernetes-sigs/security-profiles-operator/pull/991#" title="Author self-approved">saschagrunert</a>*

The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=kubernetes-sigs%2Fsecurity-profiles-operator).

The pull request process is described [here](https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process)

<details >
Needs approval from an approver in each of these files:

- ~~[OWNERS](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/OWNERS)~~ [saschagrunert]

Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
</details>
<!-- META={"approvers":[]} -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 66f9c0c41c4cb0adec3a83df7707bd5a8f9a6194 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1536641688720642048) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 5a178c78d97feb8912db3bce34e4da6302921f2d | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1536692094289055744) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 5ff98748733894d75139ff5812fe942d2d1e5863 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1536729859206680576) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 4bc3271f35277ee8ba7a681a242281ac61db8289 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1536990761176797184) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 120bdab9cdb4ae485e022af4dc170fe182f0af4a | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537014289104113664) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | d9eba641e639a230dab9e825a9466ccbb3460df2 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537045846099496960) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
saschagrunert: Interestingly, the two syscalls `sched_yield` and `rt_sigreturn` see to flake in the test. :thinking: It may be related to application teardown…
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537053604626567168) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
saschagrunert: /retest
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537343422464004096) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
saschagrunert: /retest
saschagrunert: /test pull-security-profiles-operator-test-e2e
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537355164917174272) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: PR needs rebase.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
</details>
k8s-triage-robot: The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:
- After 90d of inactivity, `lifecycle/stale` is applied
- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed

You can:
- Mark this issue or PR as fresh with `/remove-lifecycle stale`
- Mark this issue or PR as rotten with `/lifecycle rotten`
- Close this issue or PR with `/close`
- Offer to help out with [Issue Triage][1]

Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community).

/lifecycle stale

[1]: https://www.kubernetes.dev/docs/guide/issue-triage/
k8s-triage-robot: The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:
- After 90d of inactivity, `lifecycle/stale` is applied
- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed

You can:
- Mark this issue or PR as fresh with `/remove-lifecycle rotten`
- Close this issue or PR with `/close`
- Offer to help out with [Issue Triage][1]

Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community).

/lifecycle rotten

[1]: https://www.kubernetes.dev/docs/guide/issue-triage/
k8s-triage-robot: The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:
- After 90d of inactivity, `lifecycle/stale` is applied
- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
- After 30d of inactivity since `lifecycle/rotten` was applied, the PR is closed

You can:
- Reopen this PR with `/reopen`
- Mark this PR as fresh with `/remove-lifecycle rotten`
- Offer to help out with [Issue Triage][1]

Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community).

/close

[1]: https://www.kubernetes.dev/docs/guide/issue-triage/
k8s-ci-robot: @k8s-triage-robot: Closed this PR.

<details>

In response to [this](https://github.com/kubernetes-sigs/security-profiles-operator/pull/991#issuecomment-1364583142):

>The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
>
>This bot triages PRs according to the following rules:
>- After 90d of inactivity, `lifecycle/stale` is applied
>- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied
>- After 30d of inactivity since `lifecycle/rotten` was applied, the PR is closed
>
>You can:
>- Reopen this PR with `/reopen`
>- Mark this PR as fresh with `/remove-lifecycle rotten`
>- Offer to help out with [Issue Triage][1]
>
>Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community).
>
>/close
>
>[1]: https://www.kubernetes.dev/docs/guide/issue-triage/


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
</details>
k8s-ci-robot: @saschagrunert: The following tests **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests:

Test name | Commit | Details | Required | Rerun command
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537355164917174272) | true | `/test pull-security-profiles-operator-test-e2e`
pull-security-profiles-operator-build | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build/1612387735501279232) | true | `/test pull-security-profiles-operator-build`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: The following tests **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests:

Test name | Commit | Details | Required | Rerun command
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537355164917174272) | true | `/test pull-security-profiles-operator-test-e2e`
pull-security-profiles-operator-build | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build/1612387735501279232) | true | `/test pull-security-profiles-operator-build`
pull-security-profiles-operator-verify | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-verify/1612387735555805184) | true | `/test pull-security-profiles-operator-verify`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: The following tests **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests:

Test name | Commit | Details | Required | Rerun command
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1537355164917174272) | true | `/test pull-security-profiles-operator-test-e2e`
pull-security-profiles-operator-build | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build/1612387735501279232) | true | `/test pull-security-profiles-operator-build`
pull-security-profiles-operator-verify | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-verify/1612387735555805184) | true | `/test pull-security-profiles-operator-verify`
pull-security-profiles-operator-build-image | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build-image/1612387735660662784) | true | `/test pull-security-profiles-operator-build-image`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: The following tests **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests:

Test name | Commit | Details | Required | Rerun command
--- | --- | --- | --- | ---
pull-security-profiles-operator-build | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build/1612387735501279232) | true | `/test pull-security-profiles-operator-build`
pull-security-profiles-operator-verify | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-verify/1612387735555805184) | true | `/test pull-security-profiles-operator-verify`
pull-security-profiles-operator-build-image | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build-image/1612387735660662784) | true | `/test pull-security-profiles-operator-build-image`
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1612387735702605824) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: The following tests **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests:

Test name | Commit | Details | Required | Rerun command
--- | --- | --- | --- | ---
pull-security-profiles-operator-build | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build/1612387735501279232) | true | `/test pull-security-profiles-operator-build`
pull-security-profiles-operator-verify | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-verify/1612387735555805184) | true | `/test pull-security-profiles-operator-verify`
pull-security-profiles-operator-build-image | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-build-image/1612387735660662784) | true | `/test pull-security-profiles-operator-build-image`
pull-security-profiles-operator-test-e2e | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1612387735702605824) | true | `/test pull-security-profiles-operator-test-e2e`
pull-security-profiles-operator-test-unit | 19ba760c8de5dc7e51d1348988a4a47baefb6365 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-unit/1612387735606136832) | true | `/test pull-security-profiles-operator-test-unit`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 19dec60327036fbe9fa89517404f77d79b4209d5 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1631225088000921600) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | 5eb79e02e651432fdd231dcba375fadf81b2902d | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1631233783741026304) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
saschagrunert: Happy tests!

@kubernetes-sigs/security-profiles-operator-maintainers PTAL
k8s-ci-robot: @saschagrunert: 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
--- | --- | --- | --- | ---
pull-security-profiles-operator-test-e2e | cbdadc7645f4e233e2a5593daf985467adb638d6 | [link](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_security-profiles-operator/991/pull-security-profiles-operator-test-e2e/1631254820448899072) | true | `/test pull-security-profiles-operator-test-e2e`

[Full PR test history](https://prow.k8s.io/pr-history?org=kubernetes-sigs&repo=security-profiles-operator&pr=991). [Your PR dashboard](https://prow.k8s.io/pr?query=is%3Apr%20state%3Aopen%20author%3Asaschagrunert). Please help us cut down on flakes by [linking to](https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests) an [open issue](https://github.com/kubernetes-sigs/security-profiles-operator/issues?q=is:issue+is:open) when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
saschagrunert: @kubernetes-sigs/security-profiles-operator-maintainers  PTAL

Patch:
diff --git a/OWNERS b/OWNERS
index 988e5ba81..bed6d0388 100644
--- a/OWNERS
+++ b/OWNERS
@@ -2,8 +2,8 @@
 
 reviewers:
   - Vincent056
-  - ccojocar
 approvers:
+  - ccojocar
   - pjbgf
   - saschagrunert
   - JAORMX
diff --git a/dependencies.yaml b/dependencies.yaml
index 6d5069a57..fb6bd7a25 100644
--- a/dependencies.yaml
+++ b/dependencies.yaml
@@ -58,6 +58,8 @@ dependencies:
       match: cert-manager/cert-manager
     - path: hack/ci/e2e-olm.sh
       match: cert-manager/cert-manager
+    - path: hack/ci/baseprofiles.sh
+      match: cert-manager/cert-manager
 
   - name: kind
     version: 0.17.0
diff --git a/examples/baseprofile-crun.yaml b/examples/baseprofile-crun.yaml
index 7d30ba748..4b66d96c0 100644
--- a/examples/baseprofile-crun.yaml
+++ b/examples/baseprofile-crun.yaml
@@ -2,53 +2,62 @@
 apiVersion: security-profiles-operator.x-k8s.io/v1beta1
 kind: SeccompProfile
 metadata:
-  name: crun-v0.20.1
+  name: crun-v1.5
 spec:
   defaultAction: SCMP_ACT_ERRNO
   architectures:
-  - SCMP_ARCH_X86_64
+    - SCMP_ARCH_X86_64
   syscalls:
-  - action: SCMP_ACT_ALLOW
-    names:
-    - access
-    - arch_prctl
-    - brk
-    - capset
-    - chdir
-    - close
-    - close_range
-    - dup2
-    - execve
-    - exit_group
-    - fchdir
-    - fstat
-    - getcwd
-    - getegid
-    - geteuid
-    - getgid
-    - getpid
-    - getppid
-    - getuid
-    - ioctl
-    - lseek
-    - mmap
-    - mount
-    - mprotect
-    - openat
-    - openat2
-    - pivot_root
-    - prctl
-    - read
-    - rt_sigaction
-    - rt_sigprocmask
-    - select
-    - set_tid_address
-    - sethostname
-    - setresgid
-    - setresuid
-    - setsid
-    - stat
-    - statx
-    - umask
-    - umount2
-    - write
+    - action: SCMP_ACT_ALLOW
+      names:
+        - access
+        - arch_prctl
+        - brk
+        - capset
+        - chdir
+        - chmod
+        - chown
+        - close
+        - close_range
+        - dup2
+        - execve
+        - exit_group
+        - fchdir
+        - fchown
+        - fstatfs
+        - getegid
+        - geteuid
+        - getgid
+        - getuid
+        - ioctl
+        - lseek
+        - mkdirat
+        - mknodat
+        - mmap
+        - mount
+        - mprotect
+        - nanosleep
+        - newfstatat
+        - openat
+        - openat2
+        - pivot_root
+        - prctl
+        - pselect6
+        - read
+        - readlink
+        - rt_sigaction
+        - rt_sigprocmask
+        - set_tid_address
+        - setgroups
+        - sethostname
+        - setns
+        - setresgid
+        - setresuid
+        - setsid
+        - statfs
+        - statx
+        - symlinkat
+        - umask
+        - umount2
+        - unshare
+        - write
diff --git a/examples/baseprofile-runc.yaml b/examples/baseprofile-runc.yaml
index bd7291ddf..87d362cab 100644
--- a/examples/baseprofile-runc.yaml
+++ b/examples/baseprofile-runc.yaml
@@ -2,56 +2,75 @@
 apiVersion: security-profiles-operator.x-k8s.io/v1beta1
 kind: SeccompProfile
 metadata:
-  name: runc-v1.0.0
+  name: runc-v1.1.4
 spec:
   defaultAction: SCMP_ACT_ERRNO
   architectures:
-  - SCMP_ARCH_X86_64
+    - SCMP_ARCH_X86_64
   syscalls:
-  - action: SCMP_ACT_ALLOW
-    names:
-    - arch_prctl
-    - brk
-    - capget
-    - capset
-    - chdir
-    - close
-    - dup3
-    - epoll_ctl
-    - epoll_pwait
-    - execve
-    - exit_group
-    - fchdir
-    - fchown
-    - fcntl
-    - fstat
-    - fstatfs
-    - futex
-    - getcwd
-    - getdents64
-    - getpid
-    - getppid
-    - getuid
-    - ioctl
-    - mmap
-    - mount
-    - mprotect
-    - nanosleep
-    - newfstatat
-    - openat
-    - pivot_root
-    - prctl
-    - read
-    - rt_sigaction
-    - rt_sigprocmask
-    - rt_sigreturn
-    - set_tid_address
-    - setgid
-    - setgroups
-    - sethostname
-    - setuid
-    - statfs
-    - tgkill
-    - umask
-    - umount2
-    - write
+    - action: SCMP_ACT_ALLOW
+      names:
+        - arch_prctl
+        - brk
+        - capget
+        - capset
+        - chdir
+        - clone
+        - close
+        - dup3
+        - epoll_create1
+        - epoll_ctl
+        - epoll_pwait
+        - execve
+        - exit_group
+        - faccessat2
+        - fchdir
+        - fchmodat
+        - fchownat
+        - fcntl
+        - fstat
+        - fstatfs
+        - futex
+        - getdents64
+        - getpid
+        - getppid
+        - gettid
+        - getuid
+        - keyctl
+        - mkdirat
+        - mknodat
+        - mmap
+        - mount
+        - mprotect
+        - munmap
+        - nanosleep
+        - newfstatat
+        - openat
+        - pipe2
+        - pivot_root
+        - prctl
+        - pread64
+        - read
+        - readlinkat
+        - rt_sigaction
+        - rt_sigprocmask
+        - rt_sigreturn
+        - sched_getaffinity
+        - sched_yield
+        - seccomp
+        - set_robust_list
+        - set_tid_address
+        - setgid
+        - setgroups
+        - sethostname
+        - setsid
+        - setuid
+        - sigaltstack
+        - statfs
+        - symlinkat
+        - tgkill
+        - umask
+        - umount2
+        - unlinkat
+        - unshare
+        - write
diff --git a/hack/ci/baseprofiles.sh b/hack/ci/baseprofiles.sh
new file mode 100755
index 000000000..c1cba7c92
--- /dev/null
+++ b/hack/ci/baseprofiles.sh
@@ -0,0 +1,174 @@
+#!/usr/bin/env bash
+# Copyright 2022 The Kubernetes Authors.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+set -euo pipefail
+
+install_yq() {
+    echo "Installing yq"
+    go install -mod=mod github.com/mikefarah/yq/v4@latest
+    GOPATH=$(go env GOPATH)
+    export PATH=$GOPATH/bin:$PATH
+    yq --version
+}
+
+k() {
+    kubectl -n security-profiles-operator "$@"
+}
+
+k_wait() {
+    k wait --timeout 120s --for condition=ready "$@"
+}
+
+wait_for_pod_name_label() {
+    echo "Waiting for pod with label name=$1"
+
+    for ((i = 0; i < 10; i++)); do
+        FOUND=$(k get pods -l name="$1" 2>/dev/null)
+        if [[ $FOUND ]]; then
+            echo "Found pod"
+            return
+        fi
+        echo "Still waiting ($i)"
+        sleep 5
+    done
+
+    echo "Timed out waiting for pod label name=$1"
+    exit 1
+}
+
+wait_for() {
+    echo "Waiting for $*"
+    for ((i = 0; i < 10; i++)); do
+        if k get "$@" 2>/dev/null; then
+            echo "Found Kubernetes object $*"
+            return
+        fi
+        echo "Still waiting ($i)"
+        sleep 5
+    done
+
+    echo "Timed out waiting for $*"
+    exit 1
+}
+
+install_operator() {
+    kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.10.1/cert-manager.yaml
+    kubectl -n cert-manager wait --for condition=ready pod -l app.kubernetes.io/instance=cert-manager
+
+    git apply hack/deploy-localhost.patch
+    kubectl apply -f deploy/operator.yaml
+    kubectl label ns security-profiles-operator spo.x-k8s.io/enable-recording=
+
+    k_wait pod -l name=security-profiles-operator
+
+    wait_for_pod_name_label security-profiles-operator-webhook
+    k_wait pod -l name=security-profiles-operator-webhook
+
+    wait_for_pod_name_label spod
+    k_wait pod -l name=spod
+
+    wait_for spod spod
+    k patch spod spod --type=merge -p '{"spec":{"enableBpfRecorder":true}}'
+    k rollout status ds spod --timeout 360s
+    k_wait spod spod
+}
+
+record_baseprofile() {
+    echo "Recording baseprofiles"
+    PODNAME=test-pod
+    RECORDING=test-recording-$PODNAME
+
+    TMP_DIR=$(mktemp -d)
+    trap 'rm -rf $TMP_DIR' EXIT
+
+    echo "Creating profile recording"
+    k apply -f examples/profilerecording-seccomp-bpf.yaml
+
+    RUNTIMES=(runc crun)
+    for RUNTIME in "${RUNTIMES[@]}"; do
+        echo "For runtime $RUNTIME"
+        BASEPROFILE=examples/baseprofile-$RUNTIME.yaml
+
+        RC_FILE="$TMP_DIR/rc.yml"
+        cat <<EOT >"$RC_FILE"
+---
+apiVersion: node.k8s.io/v1
+kind: RuntimeClass
+metadata:
+  name: $RUNTIME
+handler: $RUNTIME
+EOT
+        echo "Creating runtime class"
+        cat "$RC_FILE"
+
+        k apply -f "$RC_FILE"
+
+        POD_FILE="$TMP_DIR/pod.yml"
+        cat <<EOT >"$POD_FILE"
+---
+apiVersion: v1
+kind: Pod
+metadata:
+  name: $PODNAME
+  labels:
+    app: alpine
+spec:
+  runtimeClassName: $RUNTIME
+  restartPolicy: Never
+  containers:
+  - name: $PODNAME
+    image: alpine:3
+    command: ["sleep", "3"]
+EOT
+        echo "Creating pod:"
+        cat "$POD_FILE"
+
+        k apply -f "$POD_FILE"
+
+        echo "Waiting for pod to be completed"
+        for ((i = 0; i < 10; i++)); do
+            if k get pods $PODNAME | grep -q Completed; then
+                echo "Pod completed"
+                break
+            fi
+            echo "Still waiting ($i)"
+            sleep 5
+        done
+
+        echo "Deleting pod"
+        k delete -f "$POD_FILE"
+
+        wait_for seccompprofile $RECORDING
+
+        echo "Patching existing base seccomp profile"
+        yq -i ".spec.syscalls = $(
+            k get seccompprofile $RECORDING -o json | jq .spec.syscalls -c
+        )" "$BASEPROFILE"
+
+        echo "Getting runtime version"
+        VERSION=$($RUNTIME --version | grep "$RUNTIME version" | grep -oP '\d+.*')
+        yq -i '.metadata.name = "'"$RUNTIME"'-v'"$VERSION"'"' "$BASEPROFILE"
+
+        echo "Deleting seccomp profile"
+        k delete seccompprofile $RECORDING
+    done
+
+    echo "Diffing output, while ignoring flaky syscalls 'rt_sigreturn', 'sched_yield' and 'tgkill'"
+    git diff --exit-code -U0 -I rt_sigreturn -I sched_yield -I tgkill examples
+}
+
+install_yq
+install_operator
+record_baseprofile
diff --git a/hack/ci/install-cri-o.sh b/hack/ci/install-cri-o.sh
index 323c8ecc6..7d7e88866 100755
--- a/hack/ci/install-cri-o.sh
+++ b/hack/ci/install-cri-o.sh
@@ -45,4 +45,8 @@ if [[ $ID == fedora ]]; then
     printf '[crio.runtime]\nselinux = true' >/etc/crio/crio.conf.d/30-selinux.conf
 fi
 
+if [[ $ID == ubuntu ]]; then
+    printf '[crio.runtime.runtimes.runc]\n' >/etc/crio/crio.conf.d/10-runc.conf
+fi
+
 systemctl enable --now crio.service
diff --git a/hack/deploy-localhost.patch b/hack/deploy-localhost.patch
index 840805a58..5e6bbf305 100644
--- a/hack/deploy-localhost.patch
+++ b/hack/deploy-localhost.patch
@@ -1,8 +1,8 @@
 diff --git a/deploy/operator.yaml b/deploy/operator.yaml
-index 6d28eddd..154fbad0 100644
+index d7bf1964..d2a9c614 100644
 --- a/deploy/operator.yaml
 +++ b/deploy/operator.yaml
-@@ -1359,7 +1359,7 @@ metadata:
+@@ -2954,7 +2954,7 @@ metadata:
    name: security-profiles-operator
    namespace: security-profiles-operator
  spec:
@@ -11,10 +11,10 @@ index 6d28eddd..154fbad0 100644
    selector:
      matchLabels:
        app: security-profiles-operator
-@@ -1382,8 +1382,8 @@ spec:
-           valueFrom:
-             fieldRef:
-               fieldPath: metadata.namespace
+@@ -2988,8 +2988,8 @@ spec:
+               fieldPath: spec.nodeName
+         - name: KUBELET_DIR
+           value: /var/lib/kubelet
 -        image: gcr.io/k8s-staging-sp-operator/security-profiles-operator:latest
 -        imagePullPolicy: Always
 +        image: localhost/security-profiles-operator:latest
diff --git a/internal/pkg/cli/recorder/consts.go b/internal/pkg/cli/recorder/consts.go
index bfb151b90..b57964ee1 100644
--- a/internal/pkg/cli/recorder/consts.go
+++ b/internal/pkg/cli/recorder/consts.go
@@ -66,66 +66,81 @@ var (
 		"capget",
 		"capset",
 		"chdir",
+		"chmod",
+		"chown",
+		"clone",
 		"close",
 		"close_range",
 		"dup2",
 		"dup3",
+		"epoll_create1",
 		"epoll_ctl",
 		"epoll_pwait",
 		"execve",
 		"exit_group",
 		"faccessat2",
 		"fchdir",
+		"fchmodat",
 		"fchown",
+		"fchownat",
 		"fcntl",
 		"fstat",
 		"fstatfs",
 		"futex",
-		"getcwd",
 		"getdents64",
 		"getegid",
 		"geteuid",
 		"getgid",
 		"getpid",
 		"getppid",
-		"getrandom",
+		"gettid",
 		"getuid",
 		"ioctl",
+		"keyctl",
 		"lseek",
+		"mkdirat",
+		"mknodat",
 		"mmap",
 		"mount",
 		"mprotect",
+		"munmap",
 		"nanosleep",
 		"newfstatat",
 		"openat",
 		"openat2",
+		"pipe2",
 		"pivot_root",
 		"prctl",
-		"prlimit64",
+		"pread64",
 		"pselect6",
 		"read",
 		"readlink",
-		"rseq",
+		"readlinkat",
 		"rt_sigaction",
 		"rt_sigprocmask",
 		"rt_sigreturn",
-		"select",
+		"sched_getaffinity",
+		"sched_yield",
+		"seccomp",
 		"set_robust_list",
 		"set_tid_address",
 		"setgid",
 		"setgroups",
 		"sethostname",
+		"setns",
 		"setresgid",
 		"setresuid",
 		"setsid",
 		"setuid",
-		"stat",
+		"sigaltstack",
 		"statfs",
 		"statx",
+		"symlinkat",
 		"tgkill",
 		"umask",
 		"umount2",
-		"uname",
+		"unlinkat",
+		"unshare",
 		"write",
 	}
 )


Test patch:
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 5c45c509b..5be8dd641 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -167,3 +167,33 @@ jobs:
         run: |
           $RUN "echo \"export E2E_TEST_FLAKY_TESTS_ONLY=true\" >> /vagrant/hack/ci/env-flatcar.sh"
           $RUN hack/ci/e2e-flatcar-dev-container.sh
+
+  baseprofiles:
+    needs: image
+    runs-on: macos-12
+    timeout-minutes: 90
+    env:
+      RUN: ./hack/ci/run-ubuntu.sh
+    steps:
+      - uses: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c # v3.3.0
+      - uses: actions/cache@69d9d449aced6a2ede0bc19182fadc3a0a42d2b0
+        with:
+          path: |
+            ~/.vagrant.d/boxes
+          key: e2e-ubuntu-${{ hashFiles('hack/ci/Vagrantfile-ubuntu') }}
+          restore-keys: e2e-ubuntu-
+      - uses: actions/download-artifact@9bc31d5ccc31df68ecc42ccf4149144866c47d8a
+        with:
+          name: image
+          path: .
+      - name: Boot Virtual Machine
+        run: make vagrant-up-ubuntu
+      - name: Show environment information
+        run: |
+          $RUN kubectl wait --for=condition=ready --timeout=60s node ubuntu2204
+          $RUN kubectl get nodes -o wide
+      - name: Set up git config
+        run: |
+          $RUN git config --global --add safe.directory /vagrant
+      - name: Record baseprofiles
+        run: $RUN hack/ci/baseprofiles.sh
diff --git a/test/tc_base_profiles_test.go b/test/tc_base_profiles_test.go
index 158973f3e..c4c26b45b 100644
--- a/test/tc_base_profiles_test.go
+++ b/test/tc_base_profiles_test.go
@@ -27,11 +27,11 @@ func (e *e2e) testCaseBaseProfile([]string) {
 	e.seccompOnlyTestCase()
 
 	baseProfilePath := "examples/baseprofile-runc.yaml"
-	baseProfileName := "runc-v1.0.0"
+	baseProfileName := "runc-v1.1.4"
 
 	if clusterType == clusterTypeVanilla && e.containerRuntime != containerRuntimeDocker {
 		baseProfilePath = "examples/baseprofile-crun.yaml"
-		baseProfileName = "crun-v0.20.1"
+		baseProfileName = "crun-v1.5"
 	}
 
 	helloProfile := fmt.Sprintf(`