Little example explain how to deploy 2 deployments, 2 services and ingress on minikube and GKE.
The example based on ingress-minikube docs.
GKE steps are optional for extended deployments.
You should have minikube (in minikube deployment) and kubectl installed.
The k keyword is alias for kubectl command.
Start the cluster with named mini1, 3 nodes with ingress addon.
minikube start -p mini1 -n 3 --addons=ingressConfigure the context in your kubectl if needed. Then, check the nodes.
❯ k get nodes
NAME STATUS ROLES AGE VERSION
mini1 Ready control-plane,master 2m25s v1.20.7
mini1-m02 Ready <none> 47s v1.20.7
mini1-m03 Ready <none> 28s v1.20.7Create namespace
k apply -f ns.yamlCreate deployments
k apply -f deployments/Create services (type: ClusterIP)
k apply -f services/Create ingress
k apply -f minikube_ingress.yaml
The ingress will deploy on ingress-nginx namespace.
You can check it's deployment by run the following command.
It will be ready as soon as you see the ADDRESS field populate with valid IP address, after 1-2 minutes.
❯ k get ingress -o wide -A
NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE
hello-ingress minikube-ingress <none> hello-world.info 192.168.49.2 80 30sIn case you running minikube on WSL, you will have to forward the ingress to the host machine using the minikube service command.
In this example will forward port 80 to 38633 and port 443 to 40685.
Each time you will start new minikube service it will pick random ports.
❯ minikube service ingress-nginx-controller -n ingress-nginx -p mini1
|---------------|--------------------------|-------------|---------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|---------------|--------------------------|-------------|---------------------------|
| ingress-nginx | ingress-nginx-controller | http/80 | http://192.168.49.2:31566 |
| | | https/443 | http://192.168.49.2:32583 |
|---------------|--------------------------|-------------|---------------------------|
🏃 Starting tunnel for service ingress-nginx-controller.
|---------------|--------------------------|-------------|------------------------|
| NAMESPACE | NAME | TARGET PORT | URL |
|---------------|--------------------------|-------------|------------------------|
| ingress-nginx | ingress-nginx-controller | | http://127.0.0.1:38633 |
| | | | http://127.0.0.1:40685 |
|---------------|--------------------------|-------------|------------------------|
🎉 Opening service ingress-nginx/ingress-nginx-controller in default browser...
👉 http://127.0.0.1:38633
🎉 Opening service ingress-nginx/ingress-nginx-controller in default browser...
👉 http://127.0.0.1:40685
❗ Because you are using a Docker driver on linux, the terminal needs to be open to run it.This ingress with deploy and listen to hello-world.info domain, so you will have to add the following record to your hosts file.
127.0.0.1 hello-world.info
Test this deployment VIA curl command.
app1:
❯ curl hello-world.info:38633
Hello, world!
Version: 1.0.0
Hostname: hello-app-66c68bf5f7-7pp5gapp2:
❯ curl hello-world.info:38633/v2
Hello, world!
Version: 2.0.0
Hostname: hello-app2-676db4445d-4wjkmapp2 with https:
❯ curl -k https://hello-world.info:40685/v2
Hello, world!
Version: 2.0.0
Hostname: hello-app2-676db4445d-k8264This following steps will use cloud resources and will charge you for that. Make sure you clean up the resources after finish to test.
First you will need to create external IP address.
gcloud compute addresses create hello-addr --global --ip-version IPV4You can check the resource with those commands
gcloud compute addresses list
gcloud compute addresses describe hello-addr --globalCreate the SSL files (private key and chain file). Then create the TLS secrets.
# generate SSL files
❯ openssl req -newkey rsa:2048 \
-x509 \
-sha256 \
-days 3650 \
-nodes \
-out fullchain.pem \
-keyout privkey.pem\
-subj "/C=US/ST=test/L=test1/O= /OU= /CN=example.com"
Generating a RSA private key
.....+++++
...........................................................+++++
writing new private key to 'privkey.pem'
# create GCP secret
❯ create secret tls web-tls \
--cert fullchain.pem --key privkey.pem -n hello-ingress
secret/web-tls created
# generate the secret YAML from the cluster
# k get secrets -n hello-ingress web-tls -o yaml > web-tls-secret.yamlThen, deploy namespace, deployments and services.
❯ k apply -f ns.yaml
namespace/hello-ingress created
❯ k apply -f deployments
deployment.apps/hello-app created
deployment.apps/hello-app2 created
❯ k apply -f services
service/svc created
service/svc2 createdFinally, deploy the GKE ingress.
The command will configure the ingress for HTTPS connections, with auto redirect the HTTP to HTTPS.
❯ k apply -f gke_ingress.yaml
ingress.networking.k8s.io/gke-hello-ingress created
frontendconfig.networking.gke.io/lb-http2https created
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent