Added support for service.spec.loadBalancerIP

[macevil]

Hello all, the possibility to configure the Service loadBalancerIP in the Helm Chart was missing. I have added it and tested it.

[webvictim]

@macevil Thanks for the PR. Looks good overall, but there are a few requests before we can merge:

1. Please add service.spec at the appropriate location in the teleport-cluster chart reference: https://github.com/gravitational/teleport/blob/master/docs/pages/kubernetes-access/helm/reference.mdx

2. Please add service.spec to https://github.com/gravitational/teleport/blob/master/examples/chart/teleport-cluster/values.schema.json

3. Please add an example which sets service.spec so it can be validated by the linter - see other examples in https://github.com/gravitational/teleport/tree/master/examples/chart/teleport-cluster/.lint

Thank you!

[webvictim]

@macevil Thanks! Looking better - just one more issue with the schema JSON.

[webvictim]

/gcbrun

[webvictim]

@russjones This one looks good to go - please approve/merge/backport as appropriate.

[russjones]

Will buddy merge in #9484.

[somethingnew2-0]

The nindent should be 2 instead of 4 here as it produces invalid yaml otherwise that looks like below

# Source: teleport-cluster/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: teleport
  namespace: cert-manager
  labels:
    app: teleport
spec:
  type: LoadBalancer
    loadBalancerIP: 1.1.1.1

and produces the following error

Error: YAML parse error on teleport-cluster/templates/service.yaml: error converting YAML to JSON: yaml: line 10: mapping values are not allowed in this context

for the following values

clusterName: teleport.example.com
service:
  spec:
    loadBalancerIP: "1.1.1.1"

[somethingnew2-0]

PR to fix #9772

[webvictim]

Handled in #9645, thanks