Refresh Kueue features overview page

[mimowo]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

To refresh the "features overview" section after a couple of new features recently added (0.9 and 0.10).

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

I have not included yet:

• HierarchicalCohorts - they are Alpha and I couldn't find a good docs link cc @gabesaba
• LocalQueue defaulting - IIUC the section focuses on people who don't use Kueue yet, to attract them, but this feature is more relevant to already users of Kueue - it rather fixes the problem with complex setup, rather than gives a new "capability" - but I'm open to discussion and including it cc @yaroslava-serdiuk

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	3a047ca
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/6763c0752be9ea0008f4ed6e

[mimowo]

cc @tenzen-y @mwielgus @dgrove-oss @kannon92 @mwysokin

[mimowo]

/hold
to avoid premature merging, I would like to hear multiple lgtm first

[yaroslava-serdiuk]

LocalQueue defaulting - IIUC the section focuses on people who don't use Kueue yet

Not really. The original issue that feature solves comes from users that familiar with Kueue: #2936

[mimowo]

Not really. The original issue that feature solves comes from users that familiar with Kueue: #2936

Yes, the LocalQueue defaulting is mostly relevant to folks who are already onboarded to Kueue, while the audience for the "feature overview" section is mostly new potential users.

[yaroslava-serdiuk]

Yes, the LocalQueue defaulting is mostly relevant to folks who are already onboarded to Kueue, while the audience for the "feature overview" section is mostly new potential users.

Oh, I see, sorry I misunderstand you.
Anyway I think it would be nice to link all features that Kueue supports.

[mimowo]

Anyway I think it would be nice to link all features that Kueue supports.

Right, let me try to accommodate that: 78169c0, wdyt?

[yaroslava-serdiuk]

/lgtm
thanks!

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 18283a981fd9ff5f5f7fdfa90505ab10a82a348b

[tenzen-y]

Just a nit.
basically, lgtm

[tenzen-y]

Thank you!

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 3e343dc72476a8c9d00c4aa5c0a7179ee4860017

[mwielgus]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mimowo, mwielgus, tenzen-y

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,tenzen-y]

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

[mimowo]

/hold cancel

[mimowo]

/cherry-pick 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.

In response to this:

/cherry-pick 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-infra-cherrypick-robot]

@mimowo: new pull request created: #3888

In response to this:

/cherry-pick 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.