Getting started with Telepresence on Linkerd services is as simple as adding an annotation to your Deployment:
The local system and the Traffic Agent connect to the Traffic Manager using its gRPC API on port 8081. Telling Linkerd to skip that port allows the Traffic Agent sidecar to fully communicate with the Traffic Manager, and therefore the rest of the Telepresence system.
Save and deploy the following YAML. Note the
config.linkerd.io/skip-outbound-ports annotation in the metadata of the pod template.
---apiVersion: apps/v1kind: Deploymentmetadata:name: quotespec:replicas: 1selector:matchLabels:app: quotestrategy:type: RollingUpdatetemplate:metadata:annotations:linkerd.io/inject: "enabled"config.linkerd.io/skip-outbound-ports: "8081,8022,6001"labels:app: quotespec:containers:- name: backendimage: docker.io/datawire/quote:0.4.1ports:- name: httpcontainerPort: 8000env:- name: PORTvalue: "8000"resources:limits:cpu: "0.1"memory: 100Mi
telepresence connect to connect to the cluster. Then
telepresence list should show the
quote deployment as
ready to intercept:
$ telepresence listquote: ready to intercept (traffic-agent not yet installed)
telepresence intercept quote --port 8080:80 to direct traffic from the
quote deployment to port 8080 on your local system. Assuming you have something listening on 8080, you should now be able to see your local service whenever attempting to access the