You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/release-notes.md
+7
Original file line number
Diff line number
Diff line change
@@ -126,6 +126,13 @@ The traffic-agent configuration was moved into a pod-annotation. This avoids syn
126
126
The clusterID was deprecated some time ago, and replaced by the ID of the namespace where the traffic-manager is installed.
127
127
</div>
128
128
129
+
## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Make telepresence connect --docker work with Rancher Desktop</div></div>
130
+
<div style="margin-left: 15px">
131
+
132
+
Rancher Desktop will start a K3s control-plane and typically expose the Kubernetes API server at `127.0.0.1:6443`. Telepresence can connect to this cluster when running on the host, but the address is not available when connecting in docker mode.
133
+
The problem is solved by ensuring that the Kubernetes API server address used when doing a `telepresence connect --docker` is swapped from 127.0.0.1 to the internal address of the control-plane node. This works because that address is available to other docker containers, and the Kubernetes API server is configured with a certificate that accepts it.
134
+
</div>
135
+
129
136
## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Rename charts/telepresence to charts/telepresence-oss.</div></div>
Copy file name to clipboardExpand all lines: docs/release-notes.mdx
+7
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,13 @@ The traffic-agent configuration was moved into a pod-annotation. This avoids syn
132
132
The clusterID was deprecated some time ago, and replaced by the ID of the namespace where the traffic-manager is installed.
133
133
</Body>
134
134
</Note>
135
+
<Note>
136
+
<Title type="bugfix">Make telepresence connect --docker work with Rancher Desktop</Title>
137
+
<Body>
138
+
Rancher Desktop will start a K3s control-plane and typically expose the Kubernetes API server at `127.0.0.1:6443`. Telepresence can connect to this cluster when running on the host, but the address is not available when connecting in docker mode.
139
+
The problem is solved by ensuring that the Kubernetes API server address used when doing a `telepresence connect --docker` is swapped from 127.0.0.1 to the internal address of the control-plane node. This works because that address is available to other docker containers, and the Kubernetes API server is configured with a certificate that accepts it.
140
+
</Body>
141
+
</Note>
135
142
<Note>
136
143
<Title type="bugfix">Rename charts/telepresence to charts/telepresence-oss.</Title>
0 commit comments