Release notes for 2.23.6

thallgren · thallgren · commit 8810c984363e · 2025-07-23T09:10:37.000+02:00
Includes a yarn upgrade
diff --git a/package.json b/package.json
@@ -56,5 +56,8 @@
   },
   "engines": {
     "node": ">=18.0"
+  },
+  "resolutions": {
+    "stylus": "github:stylus/stylus#0.62.0"
   }
 }
diff --git a/versioned_docs/version-2.23/reference/rbac.md b/versioned_docs/version-2.23/reference/rbac.md
@@ -84,8 +84,11 @@ rules:
     verbs: ["get", "watch"]
   - apiGroups: [""]
     resources: ["pods"]
-    verbs: ["get", "list", "watch"] # patch not needed when agentInjector.enabled is set to false
-
+    verbs: ["get", "list", "watch", "patch"] # patch not needed when agentInjector.enabled is set to false
+  - apiGroups: ["networking.k8s.io"]
+    resources: ["servicecidrs"]
+    verbs: ["list"]
+  
   # If argoRollouts.enabled is set to true
   - apiGroups: ["argoproj.io"]
     resources: ["rollouts"]
@@ -129,6 +132,16 @@ The permissions required by the `traffic-manager` account in a statically namesp
 the ones used in a dynamic configuration, but a `Role`/`RoleBinding` will be installed in each managed namespace instead
 of the `ClusterRole`/`ClusterRoleBinding` pair.
 
+> [!NOTE]
+> One `ClusterRole/ClusterRoleBinding` will still be present that permits the traffic-manager to list the `servicecidr` resource.
+> That resource is cluster wide, so the following cluster wide rule is required:
+>
+> ```yaml
+>   - apiGroups: ["networking.k8s.io"]
+>     resources: ["servicecidrs"]
+>     verbs: ["list"]
+> ```
+
 ## Telepresence Client Access
 
 A Telepresence client requires just a small set of RBAC permissions. The bare minimum to connect is the ability to
diff --git a/versioned_docs/version-2.23/release-notes.md b/versioned_docs/version-2.23/release-notes.md
@@ -1,6 +1,13 @@
 
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 # <img src="images/logo.png" height="64px"/> Telepresence Release Notes
+## Version 2.23.6 <span style="font-size: 16px;">(July 23)</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;">Public DNS names aren't resolved from local docker application started by Telepresence</div></div>
+<div style="margin-left: 15px">
+
+A container running using `telepresence docker-run` or `telepresence <engage-type> --docker-run` was not able to resolve public DNS names such as "google.com". The problem is caused by an undocumented behavior in Docker's internal DNS-resolver when the `--dns` flag is used in conjunction with the teleroute network, where the DNS-server no longer finds public names even thought another bridge network is connected. The problem was solved by using a fallback resolver in the Telepresence DNS resolver.
+</div>
+
 ## Version 2.23.5 <span style="font-size: 16px;">(July 20)</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;">Let docker.Start pass on --interactive to docker start.</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,13 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 
 # Telepresence Release Notes
+## Version 2.23.6 <span style={{fontSize:'16px'}}>(July 23)</span>
+<Note>
+	<Title type="bugfix">Public DNS names aren't resolved from local docker application started by Telepresence</Title>
+	<Body>
+A container running using `telepresence docker-run` or `telepresence <engage-type> --docker-run` was not able to resolve public DNS names such as "google.com". The problem is caused by an undocumented behavior in Docker's internal DNS-resolver when the `--dns` flag is used in conjunction with the teleroute network, where the DNS-server no longer finds public names even thought another bridge network is connected. The problem was solved by using a fallback resolver in the Telepresence DNS resolver.
+  </Body>
+</Note>
 ## Version 2.23.5 <span style={{fontSize:'16px'}}>(July 20)</span>
 <Note>
 	<Title type="bugfix">Let docker.Start pass on --interactive to docker start.</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.5"
-dlVersion: "v2.23.5"
+version: "2.23.6"
+dlVersion: "v2.23.6"
diff --git a/yarn.lock b/yarn.lock

Original file line number	Diff line number	Diff line change
`@@ -56,5 +56,8 @@`
`56`	`56`	`},`
`57`	`57`	`"engines": {`
`58`	`58`	`"node": ">=18.0"`
	`59`	`+ },`
	`60`	`+ "resolutions": {`
	`61`	`+ "stylus": "github:stylus/stylus#0.62.0"`
`59`	`62`	`}`
`60`	`63`	`}`