(from getambassador.io) Merge pull request #867 from datawire/khussey…

…/tun_link

Adjusting link for TUN device docs

releaseNotes.yml

@@ -28,7 +28,7 @@ items:
       - title: TCP and UDP routing via Virtual Network Interface
         body: "Telepresence will now perform routing of outbound TCP and UDP traffic via a Virtual Network Interface (VIF). The VIF is a layer 3 TUN-device that exists while Telepresence is connected. It makes the subnets in the cluster available to the workstation and will also route DNS requests to the cluster and forward them to intercepted pods. This means that pods with custom DNS configuration will work as expected. Prior versions of Telepresence would use firewall rules and were only capable of routing TCP."
         image: ./tunnel.jpg
-        docs: reference/tun-device/#both-tcp-and-udp
+        docs: reference/tun-device
         type: feature
       - title: SSH is no longer used
         body: "All traffic between the client and the cluster is now tunneled via the traffic manager gRPC API. This means that Telepresence no longer uses ssh tunnels and that the manager no longer have an <code>sshd</code> installed. Volume mounts are still established using <code>sshfs</code> but it is now configured to communicate using the sftp-protocol directly, which means that the traffic agent also runs without <code>sshd</code>. A desired side effect of this is that the manager and agent containers no longer need a special user configuration."