(February 22, 2023)
Feature: When Telepresence detects that it runs in a docker container, it will now expose its DNS on
localhost:53. This makes the
container itself a DNS server. Very handy when other containers use
Feature: A new flag,
--local-mount-port <port>will make
telepresence intercept --detailed-output --output=[yaml|json]create
a bridge to the remote SFTP service instead of starting an sshfs client. This enables the sshfs client to be started outside of the
container, and thus, mount filesystems that then can be used as source for volumes that other containers will use.
Feature: The Telepresence daemon can now run as a long-lived process in a docker container so that CLI commands that
run in other containers can use a common daemon for network access and intercepts.
Feature: A new boolean flag
--detailed-outputwas added to the
telepresence interceptcommand. It will output very
detailed information about an intercept when used together with
Pull Request 3013.
Feature: Adds two parameters
Feature: Add a parameter
Feature: Add a configuration
cluster.defaultManagerNamespacefor setting the default manager namespace.
Change: The namespace of the connected manager is now displayed in the
telepresence listcommand. This is now covered by
Bugfix: Fixed a bug when detecting VPN conflicts on macOS that removed conflicting gateway links.
Bugfix: Fixed a bug where connecting to certain VPNs that map the CIDR range of the cluster would result in no routes getting added.
Bugfix: Support ARM64 architecture
- 🔍View and search all Telepresence releases.
- 🛠️Create and share lists to track your tools.
- 🚨Setup notifications for major, security, feature or patch updates.
- 🚀Much more coming soon!