This document discusses using telepresence for local development within a Kubernetes environment. Telepresence allows running a local development process while maintaining the same network access and environment as if it were running within a Kubernetes pod. It establishes a two-way network proxy between the local machine and Kubernetes cluster. This allows services, volumes, and other resources in the cluster to be accessed from the local process, and vice versa. The document provides an example application topology and demonstrates how telepresence integrates local development into an existing Kubernetes environment for microservices development. It also outlines some lessons learned around ensuring development needs are considered.

1. Local Development using
Telepresence
Irvi Firqotul Aini
Software Engineer
Traveloka

2. $(whoami)
Previously:
Software Engineer Intern @ Bukalapak, Cermati
Currently:
Software Engineer @ Traveloka ~ 1 year-ish
@irvifa

3. Outline
Background
What is Telepresence?
Demo

4. Kubernetes is a Great
Production Environment,
But what about dev?

5. Yeay we
decide to
use K8s
OMG.. when I
tried to develop
only one part of
microservices
how can I do
that?
But, that’s
mean we need
to run all the
services all
together..
Ah.. we can
use consul
as a svc
discovery

6. Example Application
Ingress Frontend
ACL
Products
SVC
Other Cloud
Components

7. Using Docker Compose?

8. Building
Dockerimage

9. Things that We may Need
- Init containers
- Service mesh
- Etc..

10. Minikube
Initial Setup for Me was Like...

11. Lesson Learned
- I shouldn’t ignore my developers (since I’m also a product Software Engineer
too, I know exactly the pain)
- I need to listen and understands SWE problems better.. (especially for those in
the onboarding phase, I don’t want to load such a heavy info about k8s depth to
them)

12. Two-way network proxy in a pod
running in your Kubernetes cluster.
… proxies data from your Kubernetes
environment (e.g., TCP connections,
environment variables, volumes) to
the local process.

13. How It Works
Foo App
Proxy Connection svc/Bar
deploy/Bar
svc/ACL
deploy/ACL
Ingress

14. So What’s Getting Proxied?
- Networking access from the cluster
- If you use the --expose option for telepresence with a given port the pod will forward traffic it receives on
that port to your local process. This allows the Kubernetes or OpenShift cluster to talk to your local process
as if it was running in the pod.
- Networking access to the cluster
- The locally running process wrapped by telepresence has access to everything that a normal Kubernetes
pod would have access to. That means Service instances, their corresponding DNS entries, and any cloud
resources you can normally access from Kubernetes.

15. Volume Access
The root directory where all the volumes can be found will be set to the TELEPRESENCE_ROOT
environment variable in the shell run by telepresence.
You will then need to use that env variable as the root for volume paths you are opening.

16. You got Service Discovery,
Volumes, and the Same
Environments from Your Local
Machine

17. Demo

18. Thanks (^=◕ᴥ◕=^)

19. Q & A