https://cloud.google.com/solutions/best-practices-for-building-containers
https://cloud.google.com/solutions/best-practices-for-operating-containers
http2 not supported by nginx as backend server (for reverse proxy)
https://docs.nginx.com/nginx/admin-guide/security-controls/securing-http-traffic-upstream/
https://stackoverflow.com/questions/24520540/nginx-does-redirect-not-proxy
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy
warning: if u have run eval $(minikube docker-env). All commands will not be executed in the host...(check with docker ps...) -> eval $(minikube docker-env --unset)
check network that already exist Docker network ls
If u already started you should see a network called minikube. The minikube ip is on this network.
https://docs.docker.com/network/
Create a new network for setting up externals ip for your settings.
docker network create my-network --driver=bridge
docker network inspect my-network
IPAM.Config.Subnet is the subnet you should use inside your metallb config.
connect this network to the minikube container:
docker network connect my-network minikube (minikube == alias to minikube container ->docker ps)
docker network inspect my-network -> the minikube container should be added...
Configure metallb
My IPAM.Config.Subnetis172.18.0.0/16 so I given range .0.10-0.20 to metallb
Instead of all this steps. We can choose ourself the subnet:
docker network create --subnet=172.20.0.0/16 my-net
docker network connect my-net minikube
https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service
https://kubernetes.io/docs/concepts/services-networking/ingress/
https://www.stackrox.com/post/2020/01/kubernetes-networking-demystified/
Content type
Image
Digest
Size
27 MB
Last updated
over 5 years ago
docker pull ggjulio/telegraf