TAS: Fix JobSet validation.

[mbobrovskyi]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Fixed a bug that doesn't allow to validate JobSet when both kueue.x-k8s.io/podset-required-topology and kueue.x-k8s.io/podset-preferred-topology annotations are set.

Which issue(s) this PR fixes:

Fixes #4122

Special notes for your reviewer:

Does this PR introduce a user-facing change?

TAS: Fixed a bug that allows to create a JobSet with both kueue.x-k8s.io/podset-required-topology and kueue.x-k8s.io/podset-preferred-topology annotations set on the PodTemplate.

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	4dd704e
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/67a0a19dc12f2900081cbf98
😎 Deploy Preview	https://deploy-preview-4130--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.

[mbobrovskyi]

/cc @mimowo

[mszadkow]

/lgtm
thanks for tests

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c716ed31c15f8a74d8770b7fc55fea7a16ebf2c8

[mimowo]

/release-note-edit

TAS: Fixed a bug that allows to create a JobSet with both kueue.x-k8s.io/podset-required-topology and kueue.x-k8s.io/podset-preferred-topology annotations set on the PodTemplate.

[mimowo]

/approve
Thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mbobrovskyi, mimowo

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 [mimowo]

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

[mimowo]

/cherry-pick release-0.10 release-0.9
We can cherry-pick strengthened validation since this is an alpha feature still. Also, it can be easily mitigated by user by just not setting both annotations :)

[k8s-infra-cherrypick-robot]

@mimowo: once the present PR merges, I will cherry-pick it on top of release-0.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.10 release-0.9
We can cherry-pick strengthened validation since this is an alpha feature still. Also, it can be easily mitigated by user by just not setting both annotations :)

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.

[k8s-infra-cherrypick-robot]

@mimowo: new pull request created: #4132

In response to this:

/cherry-pick release-0.10 release-0.9
We can cherry-pick strengthened validation since this is an alpha feature still. Also, it can be easily mitigated by user by just not setting both annotations :)

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.

[mbobrovskyi]

/cherry-pick release-0.9

[k8s-infra-cherrypick-robot]

@mbobrovskyi: new pull request created: #4155

In response to this:

/cherry-pick release-0.9

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.