Merge pull request #252 from telepresenceio/thallgren/v2.23.2

thallgren · web-flow · commit 7e657771467c · 2025-06-27T11:19:22.000+02:00
Fix bad merge of release date
diff --git a/versioned_docs/version-2.23/release-notes.md b/versioned_docs/version-2.23/release-notes.md
@@ -1,6 +1,25 @@
 
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 # <img src="images/logo.png" height="64px"/> Telepresence Release Notes
+## Version 2.23.2
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Adding an alsoProxy subnet with 32-bit mask no longer works on macOS</div></div>
+<div style="margin-left: 15px">
+
+Routing improvements introduced in 2.23.0 surfaced a problem when using special handling of submets with 32-bit masks. The special handling now causes problems on macOS. The logic is now conditioned to only run under linux since it's no longer needed on other operating systems.
+</div>
+
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">The gather-logs command produces no cluster-side logs when connected with --docker</div></div>
+<div style="margin-left: 15px">
+
+The `telepresence gather-logs` command did not include cluster-side logs when connected using `--docker`, because it tried to store such logs in a temporary directory created by the CLI. The directory was not mounted in the daemon container. This is now changed so that the temporary directory is created under the users cache directory, which is guaranteed to be mounted on the container.
+</div>
+
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Docker volume mounts failing when connected using both --docker --proxy-via flags</div></div>
+<div style="margin-left: 15px">
+
+The volume mounter would fail when doing a `telepresence connect --docker --proxy-via all=<workload>` followed by an intercept using `--docker-run`, because the bridge that the daemon created would try to access the intercepted pod using its proxied IP. Now, the bridge will instead use the pod's real IP.
+</div>
+
 ## Version 2.23.1 <span style="font-size: 16px;">(June 24)</span>
 ## <div style="display:flex;"><img src="images/feature.png" alt="feature" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">New telepresence helm version command.</div></div>
 <div style="margin-left: 15px">
diff --git a/versioned_docs/version-2.23/release-notes.mdx b/versioned_docs/version-2.23/release-notes.mdx
@@ -7,6 +7,25 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 
 # Telepresence Release Notes
+## Version 2.23.2
+<Note>
+	<Title type="bugfix">Adding an alsoProxy subnet with 32-bit mask no longer works on macOS</Title>
+	<Body>
+Routing improvements introduced in 2.23.0 surfaced a problem when using special handling of submets with 32-bit masks. The special handling now causes problems on macOS. The logic is now conditioned to only run under linux since it's no longer needed on other operating systems.
+  </Body>
+</Note>
+<Note>
+	<Title type="bugfix">The gather-logs command produces no cluster-side logs when connected with --docker</Title>
+	<Body>
+The `telepresence gather-logs` command did not include cluster-side logs when connected using `--docker`, because it tried to store such logs in a temporary directory created by the CLI. The directory was not mounted in the daemon container. This is now changed so that the temporary directory is created under the users cache directory, which is guaranteed to be mounted on the container.
+  </Body>
+</Note>
+<Note>
+	<Title type="bugfix">Docker volume mounts failing when connected using both --docker --proxy-via flags</Title>
+	<Body>
+The volume mounter would fail when doing a `telepresence connect --docker --proxy-via all=<workload>` followed by an intercept using `--docker-run`, because the bridge that the daemon created would try to access the intercepted pod using its proxied IP. Now, the bridge will instead use the pod's real IP.
+  </Body>
+</Note>
 ## Version 2.23.1 <span style={{fontSize:'16px'}}>(June 24)</span>
 <Note>
 	<Title type="feature">New telepresence helm version command.</Title>
diff --git a/versioned_docs/version-2.23/variables.yml b/versioned_docs/version-2.23/variables.yml
@@ -1,2 +1,2 @@
-version: "2.23.1"
-dlVersion: "v2.23.1"
+version: "2.23.2"
+dlVersion: "v2.23.2"
