ResourcesGo & Kubernetes
Go & Kubernetes: Rapidly Developing Golang Microservices
Build a cloud development environment with Telepresence & Golang
Kubernetes is a container orchestration platform that enables its users to deploy and scale their microservice applications at any scale: from one service to thousands of services. However, unleashing the power of Kubernetes is often more complicated than it may initially seem — the learning curve for application developers is particularly steep. Moreover, knowing what to do is just half the battle; you must choose the best tools to do the job. So how do Go developers create a development workflow on Kubernetes that is fast and effective?
Application developers face two unique challenges when creating productive development workflows on Kubernetes.
- Most development workflows are optimized for local development, and Kubernetes applications are designed to be native to the cloud.
- As Kubernetes applications evolve into complex microservice architectures, the development environments also become more complex as every microservice adds additional dependencies. These services quickly need more resources than are available in your typical local development environment.
In this tutorial, we’ll set up a development environment for Kubernetes and make a change to a Golang microservice. Normally to develop locally, we’d have to wait for a container to build, push to the registry and deploy to see the effect of our code change. Instead, we’ll use Telepresence to see the results of our change instantly.
Step 1: Deploy a Sample Microservices Application
For our example, we’ll make code changes to a Go service running between a resource-intensive Java service and a large data store. We’ll start by deploying a sample microservice application consisting of 3 services:
- VeryLargeJavaService: A memory-intensive service written in Java that generates the front-end graphics and web pages for our application
- DataProcessingService: A Golang service that manages requests for information between the two services.
- VeryLargeDataStore: A large datastore service that contains the sample data for our Edgy Corp store.
Note: We’ve called these VeryLarge services to emphasize that your local environment may not have enough CPU and RAM, or you may not want to pay for all that extra overhead for every developer.
In this architecture diagram, you’ll notice that requests from users are routed through an ingress controller to our services. For simplicity’s sake, we’ll skip the step of deploying an ingress controller in this tutorial. If you’re ready to use Telepresence in your own setup and need a simple way to set up an ingress controller, we recommend checking out the Ambassador Edge Stack API Gateway which can be easily configured with the K8s Initializer.
Let’s deploy the sample application to your Kubernetes cluster:
Step 2: Set up your local Go development environment
We’ll need a local development environment so that we can edit the
DataProcessingService service. As you can see in the architecture diagram above, the
DataProcessingService is dependent on both the
VeryLargeJavaService and the
VeryLargeDataStore, so in order to make a change to this service, we’ll have to interact with these other services as well. Let’s get started!
1. Clone the repository for this application from GitHub.
2. Change directories into the
3. Start the Go server
4. See your service running!
5. In another terminal window,
curl localhost:3000/color to see that the service is returning
Step 3: Rapid Development with Telepresence
Instead of waiting for a container image to build, pushed to a repository, and deployed to our Kubernetes cluster we are going to use Telepresence, an open source Cloud Native Computing Foundation project. Telepresence creates a bidirectional network connection between your local development and the Kubernetes cluster to enable fast, efficient Kubernetes development.
1. Download Telepresence (~60MB):
2. Make the binary executable
3. Test Telepresence by connecting to the remote cluster
4. Send a request to the Kubernetes API server:
Great! You’ve successfully configured Telepresence. Right now, Telepresence is intercepting the request you’re making to the Kubernetes API server, and routing over its direct connection to the cluster instead of over the Internet.
Step 4: Intercept Your Golang Service
An intercept is a routing rule for Telepresence. We can create an intercept to route traffic intended for the
DataProcessingService in the cluster and instead route all of the traffic to the local version of the
DataProcessingService running on port 3000.
1. Create the intercept
2. Access the application directly with Telepresence. Visit
http://verylargejavaservice:8080. Again, Telepresence is intercepting requests from your browser and routing them directly to the Kubernetes cluster.
3. Now, we’ll make a code change. Open
edgey-corp-go/DataProcessingService/main.go and change the value of the
color variable from
orange. Save the file, stop the previous server instance and start it again with
go build main.go && ./main.
4. Reload the page in your browser and see how the color has changed from blue to orange!
That’s it! With Telepresence, we saw how quickly we can go from editing a local service to seeing how these changes will look when deployed with the larger application. When you compare it to our original process of building and deploying a container after every change, it’s very easy to see how much time you can save, especially as we make more complex changes or run even larger services.
Learn More about Telepresence
Today, we’ve learned how to rapidly use Telepresence to iterate on a Golang microservice running in Kubernetes. Instead of waiting for slow local development processes, we can iterate quickly with an instant feedback loop and a productive cloud-native development environment.
If you want to learn more about Telepresence, check out the following resources:
- Read the docs
- Watch the demo video
- Read more about Intercepts
- Learn about Preview URLs for easy collaboration with teammates
- Join our Slack channel to connect with the Telepresence community