Implement Cohort Webhook

[gabesaba]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Implements Cohort Webhook, allowing users to create Cohort API objects. Part of #79

Special notes for your reviewer:

Additional changes are needed in cache and queue before the hierarchical functionality is complete. In the current state, we have implemented first-class Cohorts: Cohorts which provide resources directly, not just from lending ClusterQueues.

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	84574cc
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/66e169b351c379000809c917

[gabesaba]

/assign @macsko

[alculquicondor]

Should we have that release note?

It was already possible to create cohorts since #2693

[gabesaba]

Should we have that release note?

It was already possible to create cohorts since #2693

Is it an option for me to write a large release note which covers all of the HierarchicalCohort changes? Then, we can link all of the relevant pull requests to it in the 0.9 release

[alculquicondor]

Is it an option for me to write a large release note which covers all of the HierarchicalCohort changes?

I actually prefer that. Or somehow preface all the changes with one common string, so that the release notes script puts them next to each other.

[alculquicondor]

/approve

[alculquicondor]

Suggested change

	var allErrs field.ErrorList
	allErrs = append(allErrs, ValidateClusterQueue(newObj)...)
	return allErrs
	return ValidateClusterQueue(newObj)

Or just remove the function. I think we used to have mutability checks before, but now everything is editable.

[gabesaba]

Changed to the suggestion, rather than removing. I think we still want validation, to make sure the values make sense upon update?

[alculquicondor]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, gabesaba

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:

• OWNERS [alculquicondor]

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

[alculquicondor]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 58635506a3e9a7203d7c8353edd25590a4f49821

[gabesaba]

/release-note-none

Only attaching release note to a single PR, where we define the API #2693

[k8s-ci-robot]

@gabesaba: you can only set the release note label to release-note-none if the release-note block in the PR body text is empty or "none".

In response to this:

/release-note-none

Only attaching release note to a single PR, where we define the API #2693

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.

[gabesaba]

/release-note-edit

NONE