docs: Update Ingress-NGINX v1.10.1 compatibility with Kubernetes v1.30

[adzinzhalifunnas]

Update the documentation to reflect the successful testing and compatibility of Ingress-NGINX v1.10.1 with Kubernetes v1.30. This change ensures that users are aware of the expanded compatibility beyond the previously documented Kubernetes v1.29 version.

Key updates:

• fixes Ingress-NGINX v1.10.1 Feature Availability on Kubernetes v1.30.2 #11494
• Modify the compatibility matrix to include Kubernetes v1.30 support
• Add a note mentioning the successful testing of Ingress-NGINX v1.10.1 on Kubernetes v1.30
• Clarify any specific considerations or caveats, if applicable, when using this combination of versions

This update aims to provide accurate and up-to-date information to users, enabling them to make informed decisions when deploying Ingress-NGINX v1.10.1 on Kubernetes v1.30.2 clusters.

[linux-foundation-easycla]

• ✅login: adzinzhalifunnas / (363c1b4)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @adzinzhalifunnas!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @adzinzhalifunnas. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx ready!

Name	Link
🔨 Latest commit	363c1b4
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/66792318bd17b9000881c6e0
😎 Deploy Preview	https://deploy-preview-11495--kubernetes-ingress-nginx.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.

[longwuyuan]

@adzinzhalifunnas thank you for this contribution.

/ok-to-test

[longwuyuan]

/lgtm

[longwuyuan]

/approve

[longwuyuan]

@adzinzhalifunnas can you please edit the PR description and add "fixes #11494"

[adzinzhalifunnas]

@adzinzhalifunnas can you please edit the PR description and add "fixes #11494"

done

[Gacko]

/lgtm

[Gacko]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.10

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.

[Gacko]

/triage accepted
/kind documentation
/priority backlgo

[k8s-ci-robot]

@Gacko: The label(s) priority/backlgo cannot be applied, because the repository doesn't have them.

In response to this:

/triage accepted
/kind documentation
/priority backlgo

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.

[Gacko]

/priority backlog

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adzinzhalifunnas, Gacko, longwuyuan

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

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

[Gacko]

/unassign

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #11500

In response to this:

/cherry-pick release-1.10

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.