FEATURE UPDATE

Multiple namespace support, runtime volume forwarding and more

Telepresence 2.0.2 available

We’re excited to announce the immediate availability of Telepresence 2.0.2. This release continues our push towards full feature parity with Telepresence 1. Telepresence 2.0.2 now:

• Supports intercepting services in multiple namespaces
• Supports forwarding volume mounts
• Supports intercepting gRPC services
• Fix behavior when Port 53 is already in use (thanks to Dave Sudia for the bug report)
• Properly handle situations when the Kubernetes context or namespace changes

We’ll be adding support for container-mode use cases next in addition to address issues that are identified by our community. Once we’re at feature parity, we’ll be releasing Telepresence 2 to the community.

Intercepting gRPC Services

Telepresence 2.0.2 supports intercepting gRPC services. Currently, Telepresence 2.0.2 does not support preview URLs from a machine via curl, or via a gRPC client. To access these types of intercepted services, you can use the x-telepresence-intercept-id header provided for you when you create an intercept.

If you’re running into this issue and need help resolving it, please reach out on Slack.

Get Started

To try it out, check out the Telepresence Quick Start today! While Telepresence supports any language, we’ve added specific tutorials in Golang and NodeJS to get you up and running faster. (More tutorials coming soon!).

If you have feedback or need help, please join #telepresence on our Slack channel. We’re happy to help!