Kops: Support customizing LoadBalancer in Cluster.spec

[tongda]

According to the code, by default, API LoadBalancer will listen on default Https port (443). However, in some places, such as China, 80 and 443 are forbidden from public internet until we put our information on record to government. But since the k8s cluster are mainly used as our internal cluster, we would prefer to use an alternative port instead of 443, such as 8888.

We have tested that setting balancer listener to port 8888 and forward to 443 of k8s apiserver could work. But every time we run kops update cluster, the k8s config will be modified to default port.

I suggest to add a field in cluster.spec like this:

spec:
  api:
    loadBalancer:
      port: 8888

Then in the code of generating AWS ELB:

Listeners: map[string]*awstasks.LoadBalancerListener{
    lbSpec.Port: {InstancePort: 443},
}

[thedarkfalcon]

Lack of customisation of ELB in cluster.spec is extremely annoying.
Everyone of our clusters will always be running additional services on different ports, I would have liked to have been able to edit the cluster.spec to also allow access to these ports via the default load balancer without post hoc changes.

[tongda]

@justinsb Excuse me for bother you. Just wonder whether this feature could be considered. Thanks.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

[arosequist]

/reopen

[k8s-ci-robot]

@arosequist: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.