Clarify Installation Document by Separating Helm Steps

[aamederen]

What this PR does / why we need it:

I found it confusing to see the helm after the list of generic steps (should I run helm install ... after I followed the steps above or is it a different way?). Also, the verification and version detection steps don't work with helm chart due to different app label (ingress-nginx vs nginx-ingress) and namespace.

This change does two things:

1. Separate helm installation from generic installation and provide version detection commands that work for helm
2. Rename Custom Service Provider Deployment to Provider Specific Steps and fix the broken link while doing so.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Couldn't find any specific github issues related to this.

Special notes for your reviewer:

[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 email the CNCF helpdesk: helpdesk@rt.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.

[codecov-io]

Codecov Report

Merging #2743 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2743   +/-   ##
=======================================
  Coverage   40.91%   40.91%           
=======================================
  Files          73       73           
  Lines        5101     5101           
=======================================
  Hits         2087     2087           
  Misses       2725     2725           
  Partials      289      289

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5039e77...0e89612. Read the comment docs.

[aamederen]

/assign @caseydavenport

[aledbf]

@aamederen please don't assign PRs manually.

[aledbf]

This works only if you are running the ingress controller in the default namespace.
By default, we use the ingress-nginx namespace

My fault, this is fine for the helm chart

[aamederen]

Correct, however the helm chart uses the default namespace by default (at least for me). The instructions for the generic deployment are the same.

[aamederen]

@aamederen please don't assign PRs manually.

@aledbf sorry, the bot was telling me to do so: Assign the PR to them by writing /assign @caseydavenport in a comment when ready.

[aledbf]

/lgtm
/approve

[aledbf]

@aamederen thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aamederen, aledbf

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

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

[aledbf]

@aamederen the build to update the docs has started. In approx ~20 minutes, you should see the update in https://kubernetes.github.io/ingress-nginx/deploy/

[aamederen]

@aledbf thanks!