Add a hugo template to highlight minimum supported version

[alculquicondor]

What would you like to be added:

Some reusable block that looks similar to the following:

And then use that for every time we mention that a feature is only available in a certain version.

Why is this needed:

Completion requirements:

This enhancement requires the following artifacts:

• Design doc
• API change
• Docs update

The artifacts should be linked in subsequent comments.

[alculquicondor]

/good-first-issue

[k8s-ci-robot]

@alculquicondor:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[ivange94]

Hi @alculquicondor, I would like to work on this. I'm new to the project and will appreciate some guidance on how to go about this.

[alculquicondor]

You can probably look at this PR for inspiration #2006

To see your work locally, you can run make site-server

[ivange94]

/assign

[ivange94]

@alculquicondor is there somewhere that we need to use this block right now? To test this I just added it to a random page but didn't commit this change. This is how it looks like.

It also looks like I didn't configure my git properly so it didn't use my actual email address and the bots say I didn't sign the license agreement. Would it be okay to edit that commit and force push to my branch or should I close the current PR and create a new one?

[tenzen-y]

It also looks like I didn't configure my git properly so it didn't use my actual email address and the bots say I didn't sign the license agreement. Would it be okay to edit that commit and force push to my branch or should I close the current PR and create a new one?

@ivange94 We're ok with either way.

[tenzen-y]

@alculquicondor is there somewhere that we need to use this block right now? To test this I just added it to a random page but didn't commit this change. This is how it looks like.

We aim to replace the warnings/notes like the ones below.

https://kueue.sigs.k8s.io/docs/tasks/manage/setup_sequential_admission/#requeuing-strategy