4 ms·

Thank you! Couple followup questions: if I have a box at home that I intend to install ubuntu to run random services, should I use minikube since it's just one

Thank you! Couple followup questions: if I have a box at home that I intend to install ubuntu to run random services, should I use minikube since it's just one node/box, or should I give it the full K8s treatment? Also, what is the difference between a reverse-proxy and a load balancer? In the K8s docs, they mention load-balancing in the 'what is ingress' section. Is it that Google made ingress both things (reverse proxy and load balancer) or that those two things are conceptually similar? If I wanted to make my local home-network machine accessible to the outside, would I want to have a reverse proxy within my network that leads to k8s/ingress, or could/should I use k8s as the exposed entrypoint to the outside world?

moondev 10y ago
If you are using ubuntu as a base you are probably better off installing k8s directly with a tool such as https://kubernetes.io/docs/getting-started-guides/kubeadm/ https://kubernetes.io/docs/getting-started-guides/kubeadm/ On ingress: You can use ingress to load balance your ingress across nodes, but it's not a service load balancer. That what services are for. Your ingress points to one or many services, which then load balance pods matching that label. Ingress IS however used in place of cloud-level load-balancers like ELB on AWS. When you choose a service type of "LoadBalancer" on a cloud platform, it provisions an elb that external traffic can go through. On-prem k8s obviously does not have that, so before ingress the only way to expose ports was by service type "NodePort" This exposes the service on a dedicated port, but it's a pain to manage because they are randomish. Ingress lets you just point at port 80, from there you can easily route to services as they come and go. For your home cluster, you can expose port 80 of your cluster to your router. Then you set up an ingress that matches the hostname. This will route to your services. It's what I do with my home cluster: https://hackernoon.com/diy-kubernetes-cluster-with-x86-stick-pcs-b0b6b879f8a7 https://hackernoon.com/diy-kubernetes-cluster-with-x86-stick...

moondev 10y ago

If you are using ubuntu as a base you are probably better off installing k8s directly with a tool such as https://kubernetes.io/docs/getting-started-guides/kubeadm/ https://kubernetes.io/docs/getting-started-guides/kubeadm/ On ingress: You can use ingress to load balance your ingress across nodes, but it's not a service load balancer. That what services are for. Your ingress points to one or many services, which then load balance pods matching that label. Ingress IS however used in place of cloud-level load-balancers like ELB on AWS. When you choose a service type of "LoadBalancer" on a cloud platform, it provisions an elb that external traffic can go through. On-prem k8s obviously does not have that, so before ingress the only way to expose ports was by service type "NodePort" This exposes the service on a dedicated port, but it's a pain to manage because they are randomish. Ingress lets you just point at port 80, from there you can easily route to services as they come and go. For your home cluster, you can expose port 80 of your cluster to your router. Then you set up an ingress that matches the hostname. This will route to your services. It's what I do with my home cluster: https://hackernoon.com/diy-kubernetes-cluster-with-x86-stick-pcs-b0b6b879f8a7 https://hackernoon.com/diy-kubernetes-cluster-with-x86-stick...