An NGINX instance used as a reverse proxy dispatch traffic to the corresponding Pod via service discovery.
Services should be created before the Proxy replication controller.
PUBLIC IP
|
|
+--------------------------------v--------------------------------+
| K8S CLUSTER | |
| +------------v------------+ |
| | SERVICE PROXY HTTPS | |
| +-------------------------+ |
| +-------------------------+ |
| | REPLICATION CONTROLLER | |
| | | |
| | POD POD | |
| | +---------+ +---------+ | |
| | | PROXY | | PROXY | | |
| | | NGINX | | NGINX | | |
| | +---------+ +---------+ | |
| +-------------------------+ |
| | | |
| +-----------------------v---+ +---v-----------------------+ |
| | SERVICE SITE ONE HTTP | | SERVICE SITE TWO HTTP | |
| +---------------------------+ +---------------------------+ |
| +---------------------------+ +---------------------------+ |
| | REPLICATION CONTROLLER | | REPLICATION CONTROLLER | |
| | | | | |
| | POD POD | | POD POD | |
| | +----------+ +----------+ | | +----------+ +----------+ | |
| | | SITE ONE | | SITE ONE | | | | SITE TWO | | SITE TWO | | |
| | | NGINX | | NGINX | | | | NGINX | | NGINX | | |
| | +----------+ +----------+ | | +----------+ +----------+ | |
| +---------------------------+ +---------------------------+ |
| |
+-----------------------------------------------------------------+
Make sure to have access to GCloud container registry, images will be pushed on their container registry.
https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/locally.md
Install necessary dependencies (Go, ETCD, Docker), clone the Kubernetes repo, then:
hack/local-up-cluster.shIn a new shell:
Make sure Kubectl is in you path: (path/to/kubernetes/repo/cluster/kubectl.sh)
cluster/kubectl.sh config set-cluster local --server=http://127.0.0.1:8080 --insecure-skip-tls-verify=true
cluster/kubectl.sh config set-context local --cluster=local
cluster/kubectl.sh config use-context local2. Run startup script (build images, push to GCloud container registry, create replications controllers and services)
To how what is happening in your cluster, you can run the following command in a different terminal:
# Show available pods
watch -n1 'cluster/kubectl.sh get pods'And in another terminal the startup script:
/bin/bash startup.shcurl -k -H "Host: www.site-one.com" https://$(kubectl get svc | grep proxy | awk '{print $2}')
curl -k -H "Host: www.site-two.com" https://$(kubectl get svc | grep proxy | awk '{print $2}')
# This command get the proxy service IP: kubectl get svc | grep proxy | awk '{print $2}'Bring down replication controllers and services
/bin/bash cleanup.sh
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent