AdmissionChecks should be configurable per flavor

[alculquicondor]

What would you like to be added:

Allow AdmissionChecks to be required for a Workload if it gets assigned a specific flavor.

Why is this needed:

The user might want to only issue a ProvisioningRequest if targeting a specific flavor, or might want different engines.

Completion requirements:

This enhancement requires the following artifacts:

• Design doc
• API change
• Docs update

The artifacts should be linked in subsequent comments.

[alculquicondor]

cc @mwielgus

[maci0]

+1

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[alculquicondor]

/assign @PBundyra

/remove-lifecycle stale