Traefik 2 with Global Static IP in gcloud

[yra-wtag]

Currently Traefik 2 is exposed using a L4 regional LB in gcloud. You can only add regional IPs for service type LoadBalancer in gcloud. However due to future possibility of moving the cluster resources in different region we need a Global Static IP.

Currently i see two scenario to make this happen

1. Use a Global TCP LB with the service and assign a static IP to it. Currently there is no tutorial on GCP to do this. Additionally it says it is not possible, Service LoadBalancers IPs needs to be regional IP. We are currently confused as Google does support Global TCP LB why it does not support with GKE Service. There no way to interface a Global TCP LB to a GKE service too.

2. Create a separate service of type Nodeport for traefik. Then expose this Nodeport Service using ingress-gce using a Global Static IP. Using this we instantly loose access to TCP and UDP services of Traefik as ingress-gce can only create a L7 HTTP(S) LB. which can only terminate http. We also lose a lot of other traefik features such as this Add option to enable proxy protocol #699

what do you guys propose for exposing a Traefik like service to the internet in Google Cloud, in a scalable future-proof way? I have read a lot of different documentation both in gcp and here. Did not find something concrete. If you guys dont have any answers can you please point me towards a source for this. Thanks

[rramkumar1]

@yra-wtag Does this help?

[yra-wtag]

@rramkumar1 Thanks. I studied it. It seemed that a lot of engineering is needed for that solution and cant really be said kubernetes like. However if thats the best solution Google has right now then we can give it a go. Is there any place in Google GKE where we can request these features to work more natively? Thanks again for your help. Please close the thread if you think there is no more information to be added for future reference.

[rramkumar1]

cc @mark-church for the feature request.

[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.