[KEP] Update KEP #993 - Add retry mechanism to AdmissionChecks

[PBundyra]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Propose changes to introduce retry mechanism for AdmissionChecks

Which issue(s) this PR fixes:

Part of #3258

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	50b9346
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/67121f0372a0e900081ac7bb
😎 Deploy Preview	https://deploy-preview-3261--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[PBundyra]

/assign @mimowo
cc @mwielgus @yaroslava-serdiuk

[mimowo]

It this configuration going to be used to configure the mechanism based on this hard-coded values:

kueue/pkg/controller/admissionchecks/provisioning/controller.go

Lines 54 to 56 in 9332a5a

	defaultMaxRetries = 3
	defaultMinBackoffSeconds = 60 // 1 min
	defaultMaxBackoffSeconds = 1800 // 30 min

, or is it going to be yet another mechanism?

Please clarify in the KEP, I would prefer to make the existing mechanism configurable and we already have an issue for it #1353. If we reuse the mechanism, can we reuse the same defaults, or state clearly that we are changing the defaults.

[mimowo]

No need for the tags in the global configuration as this is not CRD.

[mimowo]

you can drop it.

[trasc]

In my opinion we should let individual admission check controllers implement their own retry policy, not all ACCs need this and having another actor managing its ACStates makes room for conflicts or needs additional logic to avoid them.