CNF-8809: admission: add new admission for handling shared cpus request

[Tal-or]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adding a new mutation plugin that handles the following:

1. In case of workload.openshift.io/enable-shared-cpus request, it
   adds an annotation to hint runtime about the request. runtime
   is not aware of extended resources, hence we need the annotation.
2. It validates the pod's QoS class and return an error if it's not a
   guaranteed QoS class
3. It validates that no more than a single resource is being request.
4. It validates that the pod deployed in a namespace that has mixedcpus
   workloads allowed annotation.

Which issue(s) this PR fixes:

Fixes # NONE

Special notes for your reviewer:

• The Mixed-CPUs feature allows guaranteed workloads to have an access for both isolated and shared cpus.
• This PR alone doesn't enable the feature functionality, there will be following PRs for that.
• Related to CNF-8326: advertise shared cpus for mixed cpus feature #1795

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/openshift/enhancements/commit/76ea48a88bca15ef6157aacf90b8544a763e6075

[openshift-ci-robot]

@Tal-or: This pull request references CNF-8809 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it:

Add new admission for handling shared cpus

Which issue(s) this PR fixes:

Fixes # NONE

Special notes for your reviewer:

Not reviewable yet

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/openshift/enhancements/commit/76ea48a88bca15ef6157aacf90b8544a763e6075

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/test-infra repository.

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 458dce6|WIP: admission: add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[Tal-or]

/retest

[Tal-or]

/retest

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 3c2f4a4|WIP: admission: add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 58959b0|WIP: admission: add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 9232d25|UPSTREAM: : add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@Tal-or: This pull request references CNF-8809 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adding a new mutation plugin that handles the following:

1. In case of workload.openshift.io/enabled-shared-cpus request, it
   adds an annotation to hint runtime about the request. runtime
   is not aware of extended resources, hence we need the annotation.
2. It validates the pod's QoS class and return an error if it's not a
   guaranteed QoS class
3. It validates that no more than a single resource is being request.

Which issue(s) this PR fixes:

Fixes # NONE

Special notes for your reviewer:

• The Mixed-CPUs feature allows guaranteed workloads to have an access for both isolated and shared cpus.
• This PR alone doesn't enable the feature functionality, there will be following PRs for that.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/openshift/enhancements/commit/76ea48a88bca15ef6157aacf90b8544a763e6075

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/test-infra repository.

[openshift-ci-robot]

@Tal-or: This pull request references CNF-8809 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adding a new mutation plugin that handles the following:

1. In case of workload.openshift.io/enabled-shared-cpus request, it
   adds an annotation to hint runtime about the request. runtime
   is not aware of extended resources, hence we need the annotation.
2. It validates the pod's QoS class and return an error if it's not a
   guaranteed QoS class
3. It validates that no more than a single resource is being request.

Which issue(s) this PR fixes:

Fixes # NONE

Special notes for your reviewer:

• The Mixed-CPUs feature allows guaranteed workloads to have an access for both isolated and shared cpus.
• This PR alone doesn't enable the feature functionality, there will be following PRs for that.
• Related to CNF-8326: advertise shared cpus for mixed cpus feature #1795

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/openshift/enhancements/commit/76ea48a88bca15ef6157aacf90b8544a763e6075

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/test-infra repository.

[Tal-or]

/test unit

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 86f602b|UPSTREAM: : add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@Tal-or: This pull request references CNF-8809 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adding a new mutation plugin that handles the following:

1. In case of workload.openshift.io/enable-shared-cpus request, it
   adds an annotation to hint runtime about the request. runtime
   is not aware of extended resources, hence we need the annotation.
2. It validates the pod's QoS class and return an error if it's not a
   guaranteed QoS class
3. It validates that no more than a single resource is being request.
4. It validates that the pod deployed in a namespace that has mixedcpus
   workloads allowed annotation.

Which issue(s) this PR fixes:

Fixes # NONE

Special notes for your reviewer:

• The Mixed-CPUs feature allows guaranteed workloads to have an access for both isolated and shared cpus.
• This PR alone doesn't enable the feature functionality, there will be following PRs for that.
• Related to CNF-8326: advertise shared cpus for mixed cpus feature #1795

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]:  https://github.com/openshift/enhancements/commit/76ea48a88bca15ef6157aacf90b8544a763e6075

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/test-infra repository.

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 6335c48|UPSTREAM: : add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[Tal-or]

/retest

[rphillips]

/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 9f68be2 and 2 for PR HEAD 6335c48 in total

[Tal-or]

/retest

[Tal-or]

/test unit

[Tal-or]

/retest

[Tal-or]

/test unit

[Tal-or]

/test unit

[Tal-or]

/test unit

[Tal-or]

/test unit

[openshift-ci-robot]

@Tal-or: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• ac7efb4|UPSTREAM: : add new admission for handling shared cpus: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[rphillips]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: rphillips, Tal-or

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:

• DOWNSTREAM_OWNERS

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

[openshift-ci]

@Tal-or: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-hyperkube-container-v4.16.0-202312080609.p0.g7aa0a74.assembly.stream for distgit openshift-enterprise-hyperkube.
All builds following this will include this PR.