Release notes for 2.24.1

thallgren · thallgren · commit 5d9a020dbdcd · 2025-08-31T19:02:45.000+02:00
Signed-off-by: Thomas Hallgren &lt;thomas@tada.se&gt;
diff --git a/versioned_docs/version-2.24/reference/cli/telepresence_genyaml_config.md b/versioned_docs/version-2.24/reference/cli/telepresence_genyaml_config.md
@@ -17,7 +17,7 @@ Generate YAML for the agent's entry in the telepresence-agents configmap. See ge
 
 ### Flags:
 ```
-      --agent-image string         The qualified name of the agent image (default "ghcr.io/telepresenceio/tel2:2.24.0")
+      --agent-image string         The qualified name of the agent image (default "ghcr.io/telepresenceio/tel2:2.24.1")
       --agent-port uint16          The port number you wish the agent to listen on. (default 9900)
   -h, --help                       help for config
   -i, --input string               Path to the yaml containing the workload definition (i.e. Deployment, StatefulSet, etc). Pass '-' for stdin.. Mutually exclusive to --workload
diff --git a/versioned_docs/version-2.24/release-notes.md b/versioned_docs/version-2.24/release-notes.md
@@ -1,6 +1,19 @@
 
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 # <img src="images/logo.png" height="64px"/> Telepresence Release Notes
+## Version 2.24.1
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">A `telepresence connect --docker` would fail with some k3s configurations</div></div>
+<div style="margin-left: 15px">
+
+Telepresence would fail to connect to a k3s cluster unless the cluster's IP was a loopback address. This is now changed so that any IP:port combination is accepted as long as a container can be found that defines a mapping for it.
+</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;">[Restore default value for agent-state.yaml in the traffic-manager configmap](https://github.com/telepresenceio/telepresence/pull/3953)</div></div>
+<div style="margin-left: 15px">
+
+The value was previously an empty string which caused problems when when Argo CD tried to synchronize it.
+</div>
+
 ## Version 2.24.0 <span style="font-size: 16px;">(August 25)</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;">[Support for Docker Compose](howtos/docker-compose)</div></div>
 <div style="margin-left: 15px">
diff --git a/versioned_docs/version-2.24/release-notes.mdx b/versioned_docs/version-2.24/release-notes.mdx
@@ -7,6 +7,19 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 
 # Telepresence Release Notes
+## Version 2.24.1
+<Note>
+	<Title type="bugfix">A `telepresence connect --docker` would fail with some k3s configurations</Title>
+	<Body>
+Telepresence would fail to connect to a k3s cluster unless the cluster's IP was a loopback address. This is now changed so that any IP:port combination is accepted as long as a container can be found that defines a mapping for it.
+  </Body>
+</Note>
+<Note>
+	<Title type="bugfix" docs="https://github.com/telepresenceio/telepresence/pull/3953">Restore default value for agent-state.yaml in the traffic-manager configmap</Title>
+	<Body>
+The value was previously an empty string which caused problems when when Argo CD tried to synchronize it.
+  </Body>
+</Note>
 ## Version 2.24.0 <span style={{fontSize:'16px'}}>(August 25)</span>
 <Note>
 	<Title type="feature" docs="howtos/docker-compose">Support for Docker Compose</Title>
diff --git a/versioned_docs/version-2.24/variables.yml b/versioned_docs/version-2.24/variables.yml
@@ -1,2 +1,2 @@
-version: "2.24.0"
-dlVersion: "v2.24.0"
+version: "2.24.1"
+dlVersion: "v2.24.1"
