Docs: add documentation about default ingress helm value, corrections to only ingress section

[Frederik-Baetens]

What this PR does / why we need it:

Documentation about setting the default ingressclass annotation with helm was missing. Also this section could be interpreted as recommending setting a default ingressClass when running other ingresses besides ingress-nginx. While that is sometimes what the user wants, I don't think it's wise to recommend doing so to all users with multiple ingresses. The documentation has been changed to only recommend setting a default ingressClass when only running one ingress controller.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

How Has This Been Tested?

I rendered the docs with mkdocs

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Frederik-Baetens (d55b2592874228d6bccabb74e1252f9e0cf4985e, f03ee13ec3fdb69ed49bc18b9c05dab90f5e6664)

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @Frederik-Baetens!

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 @Frederik-Baetens. 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/test-infra repository.

[Frederik-Baetens]

Also your CLA process is a bit intrusive. Requiring a physical mailing adress for all contributors seems quite excessive. I've also signed a CLA with google (also transferring IP rights), and their process was significantly smoother. Why do I even need to sign 2 separate CLA's? (one easycla and one linux foundation cla)?

[rikatz]

will review the PR this week, but answering about the CLA: it's an org wide requirement (and also CNCF) and we are in the middle of migration to EasyCLA, so this is why both of them appears.

About mailing, etc etc it's out of our scope of control, as we are part of the org :)

[Frederik-Baetens]

I have rebased this pr, in doing so keeping the style changes that were committed to main.

If it's desirable, i can also omit the second commit in this pr, since it's a more opinionated change.

[longwuyuan]

@Frederik-Baetens , would it work for you to squash your commits

[iamNoah1]

/triage accepted
/priority important-soon
/kind documentation

@longwuyuan I think if we add the following label it should do it while merging, let's try :)
/label tide/merge-method-squash
@Frederik-Baetens thx
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Frederik-Baetens, iamNoah1

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:

• docs/OWNERS [iamNoah1]

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

[iamNoah1]

@longwuyuan worked

[longwuyuan]

good job @iamNoah1