Skip to content

Commit

Permalink
Prepare v2.21.3
Browse files Browse the repository at this point in the history
Signed-off-by: Thomas Hallgren <[email protected]>
  • Loading branch information
thallgren committed Feb 6, 2025
1 parent 939a51d commit 2e00a41
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ docDescription: >-
customizable development environments.
items:
- version: 2.21.3
date: (TBD)
date: 2025-02-06
notes:
- type: bugfix
title: Using the --proxy-via flag would sometimes cause connection timeouts.
Expand Down
2 changes: 1 addition & 1 deletion docs/release-notes.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

[comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
# <img src="images/logo.png" height="64px"/> Telepresence Release Notes
## Version 2.21.3
## Version 2.21.3 <span style="font-size: 16px;">(February 6)</span>
## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Using the --proxy-via flag would sometimes cause connection timeouts.</div></div>
<div style="margin-left: 15px">

Expand Down
2 changes: 1 addition & 1 deletion docs/release-notes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
[comment]: # (Code generated by relnotesgen. DO NOT EDIT.)

# Telepresence Release Notes
## Version 2.21.3
## Version 2.21.3 <span style={{fontSize:'16px'}}>(February 6)</span>
<Note>
<Title type="bugfix">Using the --proxy-via flag would sometimes cause connection timeouts.</Title>
<Body>Typically, a `telepresence connect --proxy-via <subnet>=<workflow>` would fail with a "deadline exceeded" message when several workloads were present in the namespace, the one targeted by the proxy-via didn't yet have an agent installed, and other workloads had an agent. This was due to a race condition in the logic for the agent-based port-forwards in the root daemon. The conditions causing this race are now eliminated.</Body>
Expand Down
2 changes: 1 addition & 1 deletion go.mod
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ require (
github.com/spf13/pflag v1.0.5
github.com/stretchr/testify v1.10.0
github.com/telepresenceio/go-fuseftp/rpc v0.5.0
github.com/telepresenceio/telepresence/rpc/v2 v2.21.3-rc.0
github.com/telepresenceio/telepresence/rpc/v2 v2.21.3
github.com/vishvananda/netlink v1.3.0
golang.org/x/exp v0.0.0-20241210194714-1829a127f884
golang.org/x/net v0.32.0
Expand Down
2 changes: 1 addition & 1 deletion pkg/vif/testdata/router/go.mod
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ require (
github.com/rogpeppe/go-internal v1.13.1 // indirect
github.com/spf13/cobra v1.8.1 // indirect
github.com/spf13/pflag v1.0.5 // indirect
github.com/telepresenceio/telepresence/rpc/v2 v2.21.3-rc.0 // indirect
github.com/telepresenceio/telepresence/rpc/v2 v2.21.3 // indirect
github.com/vishvananda/netlink v1.3.0 // indirect
github.com/vishvananda/netns v0.0.5 // indirect
github.com/x448/float16 v0.8.4 // indirect
Expand Down

0 comments on commit 2e00a41

Please sign in to comment.