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
+6
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,12 @@ namespaceSelector:
72
72
The output of the `telepresence list` command will now include the workload kind (deployment, replicaset, statefulset, or rollout) in all entries.
73
73
</div>
74
74
75
+
## <div style="display:flex;"><img src="images/change.png" alt="change" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Make the DNS recursion check configurable and turn it off by default.</div></div>
76
+
<div style="margin-left: 15px">
77
+
78
+
Very few systems experience a DNS recursion lookup problem. It can only occur when the cluster runs locally and the cluster's DNS is configured to somehow use DNS server that is started by Telepresence. The check is therefore now configurable through the client setting `dns.recursionCheck`, and it is `false` by default.
79
+
</div>
80
+
75
81
## <div style="display:flex;"><img src="images/change.png" alt="change" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Trigger the mutating webhook with Kubernetes eviction objects instead of patching workloads.</div></div>
Copy file name to clipboardExpand all lines: docs/release-notes.mdx
+4
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,10 @@ namespaceSelector:
68
68
<Title type="feature">List output includes workload kind.</Title>
69
69
<Body>The output of the `telepresence list` command will now include the workload kind (deployment, replicaset, statefulset, or rollout) in all entries.</Body>
70
70
</Note>
71
+
<Note>
72
+
<Title type="change">Make the DNS recursion check configurable and turn it off by default.</Title>
73
+
<Body>Very few systems experience a DNS recursion lookup problem. It can only occur when the cluster runs locally and the cluster's DNS is configured to somehow use DNS server that is started by Telepresence. The check is therefore now configurable through the client setting `dns.recursionCheck`, and it is `false` by default.</Body>
74
+
</Note>
71
75
<Note>
72
76
<Title type="change">Trigger the mutating webhook with Kubernetes eviction objects instead of patching workloads.</Title>
73
77
<Body>Instead of patching workloads, or scaling the workloads down to zero and up again, Telepresence will now create policy/v1 Eviction objects to trigger the mutating webhook. This causes a slight change in the traffic-manager RBAC. The `patch` permissions are no longer needed. Instead, the traffic-manager must be able to create "pod/eviction" objects.</Body>
0 commit comments