Cant set load balancer scheme on deployment

[sean-mcgimpsey]

Were unable to set the load balancer scheme (internal / internet-facing) on the ingress-controller deployment.
We'd ideally like to have two deployments of this controller (1 - internal, 1 - internet-facing).

Looking at the documentation, i would have thought passing the arg --scheme=internal to the controller deployment would work, however it is not recognised as an argument. For example;

-----
        args:
          - "--ip-addr-type=dualstack"
          - "--scheme=internal"
          - "--health-check-port=32080" # Using nginx ingress
          - "--health-check-path=/healthz"
          - "--target-port=32080" # Using nginx ingress
-----

I've had a look at controller.go, and it looks as though it isn't possible to define the scheme at the deployment level - only ingress, with annotations.

It would be really good to be able to define this at the deployment level.

[mikkeloscar]

Seems like a reasonable feature. PRs are ofc. welcome, otherwise I may try to take a look at it in the near future.