Setting Up an EXTERNAL-IP for Local LoadBalancer Service
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4wanGkf5INv7kGo6r-AMoyFFaSTi9eLnXOuSeVojF3QAA2lfR-7-4JolRr_J2e7YNthB1SXn-p7nBxJZKLwaEBnjsrwtn_C5wZGr4U36FQWGJVYEARyVaucmukCPLE-WJbpvt5vqeRQRzz57JvQQ8WiDuFqn9cKQ4iY7qoVrZOe5fQ-9PPcaOyPHYYPU/s16000/image.png)
Introduction If you've used a LoadBalancer service from a Cloud Provider , you'll know how convenient it is to have an EXTERNAL-IP assigned automatically. However, when using local Kubernetes , the default setting doesn't provide an EXTERNAL-IP . Building on our previous discussion, this guide will show you how to use ` cloud-provider-kind ` to assign an EXTERNAL-IP to your local LoadBalancer service . First, make sure you've set up your local Kubernetes using Kind as outlined in my previous guide. This is necessary to proceed with the next steps. Installing cloud-provider-kind Since this is a Go package , you'll need to install Go first. Then, you can install the package with the following steps: go install sigs.k8s.io/cloud-provider-kind@latest Then execute command to use: cloud-provider-kind Keep in mind that you need to keep the terminal running while using Kubernetes to create the EXTERNAL-IP . Testing with local EXTERNAL-IP Create a deployment and e