fix: Ingress docs

[groodt]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[simster7]

Thanks!

[omerfsen]

There is no need to define LoadBalancer on Svc also it exposes argo-server twice with both Ingress AND LoadBalancer which is a waste of resource so only adding BASE_HREF env variable to deployment AND creating ingress like:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: argowf-server-http-ingress
  namespace: {{argowf_ns}}
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: argo-server
          servicePort: 2746
        path: /{{argowf_path}}(/|$)(.*)
    host: {{services_subdomain}}.{{environment_domain}}
  tls:
  - hosts:
    - {{services_subdomain}}.{{environment_domain}}
    secretName: {{argowf_secret}} # do not change, this is provided by Argo Workflow

is enough.