Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/khaledalam/k8s-gcp-geo-distribution

Kubernetes and GCP infrastructure for custom traffic routing based on user geo-location.
https://github.com/khaledalam/k8s-gcp-geo-distribution

gcp geolocation ingress ingress-controller ip k8s kubernetes python routing traffic

Last synced: 6 days ago
JSON representation

Kubernetes and GCP infrastructure for custom traffic routing based on user geo-location.

Host: GitHub
URL: https://github.com/khaledalam/k8s-gcp-geo-distribution
Owner: khaledalam
Created: 2023-06-15T22:39:01.000Z (over 1 year ago)
Default Branch: main
Last Pushed: 2023-06-17T00:27:38.000Z (over 1 year ago)
Last Synced: 2024-01-27T08:36:17.963Z (11 months ago)
Topics: gcp, geolocation, ingress, ingress-controller, ip, k8s, kubernetes, python, routing, traffic
Language: Python
Homepage:
Size: 483 KB
Stars: 1
Watchers: 1
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md

Awesome Lists containing this project

README

        # k8s-gcp-geo-distribution

Routing traffic based on user geo-location using Kubernetes(K8s) and Google Cloud Platform(GCP) infrastructure.

[![Docker Pulls](https://img.shields.io/docker/pulls/khaledalam/k8s-gcp-geo-distribution.svg)](https://hub.docker.com/r/khaledalam/k8s-gcp-geo-distribution/)

[![Docker Version](https://img.shields.io/docker/v/khaledalam/k8s-gcp-geo-distribution?sort=semver)](https://hub.docker.com/r/khaledalam/k8s-gcp-geo-distribution/)

![Build Docker-Image-CI](https://github.com/khaledalam/k8s-gcp-geo-distribution/workflows/Docker-Image-CI/badge.svg)

![Deploy GKE](https://github.com/khaledalam/k8s-gcp-geo-distribution/workflows/Build-and-Deploy-to-GKE/badge.svg)

APP has 2 different versions (determined by env var `APP_COUNTRY`) Override by K8s(`spec.containers.env`):

- US 

- UAE

Each version placed on a K8s deployment<->service.

### Diagram:



K8s resources:

```

NAME                              READY   STATUS    RESTARTS   AGE

pod/deploy-uae-5979b498c4-267r4   1/1     Running   0          9s

pod/deploy-uae-5979b498c4-r986l   1/1     Running   0          9s

pod/deploy-us-77db5f8549-mrtpc    1/1     Running   0          9s

pod/deploy-us-77db5f8549-xv57c    1/1     Running   0          9s

NAME              TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE

service/srv-uae   LoadBalancer   10.108.10.19          80:30730/TCP   9s

service/srv-us    LoadBalancer   10.105.232.173        80:31591/TCP   9s

NAME                         READY   UP-TO-DATE   AVAILABLE   AGE

deployment.apps/deploy-uae   2/2     2            2           9s

deployment.apps/deploy-us    2/2     2            2           9s

NAME                                    DESIRED   CURRENT   READY   AGE

replicaset.apps/deploy-uae-5979b498c4   2         2         2       9s

replicaset.apps/deploy-us-77db5f8549    2         2         2       9s

NAME                                CLASS   HOSTS                 ADDRESS   PORTS   AGE

ingress.networking.k8s.io/ing-geo   nginx   k8s-ingress-url.com             80      9s

```

Routing:

- 1st method: `(costly solution)`

    - Used GCP function and node package [geoip-lite](https://github.com/geoip-lite/node-geoip)(based on maxmind) for locating the user ip country and routing the traffic to k8s ingress paths `/us` or `/uae`.

      - GCP function 2nd-gen has more `Runtime, build, connections and security settings` such as Concurrency(Maximum concurrent requests per instance).

  - Improvements:

    - Replace GCP function with lower price solution

    - DB update mechanism, Caching maxmind calls, ..

    - ...

- Other methods: `investigating ingress-nginx custom annotation and other solutions`