Allow Deploying Multiple Ingress Controllers per Cluster

[Dean-Coakley]

Proposed changes

Re: #528
Fixes: #549

All names of resources created by a deployment must be unique.

• By default helm chart now prepends release name to all resources it creates to ensure no conflicts occur when deploying 2 or more ingress controllers in the same namespace.

• leaderLockName now set on daemonset

• Add missing docs about defaultTLS secret to values.yaml

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto master
• I will ensure my PR is targeting the master branch and pulling from my branch from my own fork

[dlapcenko]

controller.reportIngressStatus.externalService name mismatch has to be addressed.

[dlapcenko]

@Dean-Coakley could metadata.namespace: {{ .Release.Namespace }} be added to templates as part of this PR please? is necessary for certain deploy processes (spinnaker helm).

[Dean-Coakley]

@dlapcenko That change is reasonable. We'll land that change in a separate PR shortly - as it's not related to: #528

[pleshakov]

Please see my suggestions.

Also, could you update the description of the PR so that it reflects that PR changes?

[martialonline]

Looking good.