use kueue workloads in place of workloads for future workload aware scheduling

[kannon92]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Use kueueworkloads instead of workloads to not pick in-tree workload object in future

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	a295662
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/69612cde34d6c80008f42b32
😎 Deploy Preview	https://deploy-preview-8478--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 project configuration.

[kannon92]

cc @mimowo @tenzen-y

[mbobrovskyi]

I’m wondering if we need to add a kueueworkloads alias in that case. If I remember correctly, we added only kueueworkload, right?

[mimowo]

Good point, let's add kueueworkloads.

[tenzen-y]

I'm wondering if we really need to replace workloads with alias name in documentations.

We can consider replacing that with workloads.kueue.x-k8s.io in the doc.

[kannon92]

We can consider replacing that with workloads.kueue.x-k8s.io in the doc.

On second thought I agree with you actually.

From what @JoelSpeed has mentioned to me, the only thing that is really actually guaranteed to work is to use the full path with getting these resources. So it may be best to use that to make sure we don't hit any ambiguity in our documentation.

I'll update this to use the proper path.

[tenzen-y]

We can consider replacing that with workloads.kueue.x-k8s.io in the doc.

On second thought I agree with you actually.

From what @JoelSpeed has mentioned to me, the only thing that is really actually guaranteed to work is to use the full path with getting these resources. So it may be best to use that to make sure we don't hit any ambiguity in our documentation.

I'll update this to use the proper path.

SGTM, thank you for your effort 🥇

[mimowo]

Thank you 👍
/lgtm
/approve
/cherrypick website
Since this would always work then we can already cherrypick to website

[k8s-infra-cherrypick-robot]

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

Details

In response to this:

Thank you 👍
/lgtm
/approve
/cherrypick website
Since this would always work then we can already cherrypick to website

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-ci-robot]

LGTM label has been added.

Details

Git tree hash: 5db450132200e6d20728909d2012273e7dd2116f

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• site/OWNERS [mimowo]

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

[k8s-infra-cherrypick-robot]

@mimowo: new pull request created: #8504

Details

In response to this:

Thank you 👍
/lgtm
/approve
/cherrypick website
Since this would always work then we can already cherrypick to website

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.