Merge pull request #244 from telepresenceio/thallgren/v2.22.5

Release notes for 2.22.5

Author: thallgren

versioned_docs/version-2.22/release-notes.md

@@ -1,6 +1,32 @@
 
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 # <img src="images/logo.png" height="64px"/> Telepresence Release Notes
+## Version 2.22.5 <span style="font-size: 16px;">(May 29)</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;">Unable to correctly determine service CIDR with Kubernetes >= 1.33</div></div>
+<div style="margin-left: 15px">
+
+Starting with Kubernetes 1.33, the strategy of extracting the cluster's service CIDR from an error message no longer works because the error message has changed. The root cause for this is that Kubernetes introduced the ability to use [Multiple Service CIDRs](https://gist.github.com/aojea/c20eb117bf1c1214f8bba26c495be9c7). Since `ServiceCIDR` is now a resource, it can be easily retrieved (and modified) using standard Kubernetes client API calls, and this is what the traffic manager will use going forward.
+The fix required an addition to the traffic-manager's RBAC, granting it sufficient permissions to list `networking.k8s.io/servicecidrs`. A future enhancement will allow the traffic manager to watch for service CIDR changes.
+</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;">Helm chart schema type for nodeSelector was incorrect</div></div>
+<div style="margin-left: 15px">
+
+The Helm chart schema for the `nodeSelector` value was incorrect. Kubernetes defines different types for nodeSelector (inside PodSpec objects) and NodeSelector (inside NodeAffinity, VolumeNodeAffinity and a bunch of other places). The schema was changed to use the correct type. The name `nodeSelector` is still used in the Helm chart so this change is backwards compatible.
+</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;">Pods with container ports named the same caused intercept to fail</div></div>
+<div style="margin-left: 15px">
+
+Intercept container ports now have numbers appended to them if there are multiple ports from multiple containers with the same name. This bugfix works around an issue where Kubernetes allows multiple port definitions in a pod spec to have the same name.
+</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;">Don't include k8s-defs.json to chart package</div></div>
+<div style="margin-left: 15px">
+
+The k8s-defs.json was unnecessarily included to the Helm chart package and this increased the Helm release secret size so much that it could prevent installation of the Helm chart depending on k8s settings. To fix this k8s-defs.json is not included to the Helm chart anymore.
+</div>
+
 ## Version 2.22.4 <span style="font-size: 16px;">(April 26)</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;">Don't require internet access when installing the traffic-manager using Helm</div></div>
 <div style="margin-left: 15px">
@@ -101,7 +127,7 @@ Key differences between `replace` and `intercept`:
 
 1. **Scope:** The `replace` command targets and affects an entire container, impacting all its traffic, while
    an `intercept` targets specific services and/or service/container ports.
-2. **Port Declarations:** Remote ports specified using the `--port` flag are container ports. 
+2. **Port Declarations:** Remote ports specified using the `--port` flag are container ports.
 3. **No Default Port:** A `replace` can occur without intercepting any ports.
 4. **Container State:** During a `replace`, the original container is no longer active within the cluster.
 

versioned_docs/version-2.22/release-notes.mdx

@@ -7,6 +7,32 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 
 # Telepresence Release Notes
+## Version 2.22.5 <span style={{fontSize:'16px'}}>(May 29)</span>
+<Note>
+	<Title type="bugfix">Unable to correctly determine service CIDR with Kubernetes >= 1.33</Title>
+	<Body>
+Starting with Kubernetes 1.33, the strategy of extracting the cluster's service CIDR from an error message no longer works because the error message has changed. The root cause for this is that Kubernetes introduced the ability to use [Multiple Service CIDRs](https://gist.github.com/aojea/c20eb117bf1c1214f8bba26c495be9c7). Since `ServiceCIDR` is now a resource, it can be easily retrieved (and modified) using standard Kubernetes client API calls, and this is what the traffic manager will use going forward.
+The fix required an addition to the traffic-manager's RBAC, granting it sufficient permissions to list `networking.k8s.io/servicecidrs`. A future enhancement will allow the traffic manager to watch for service CIDR changes.
+  </Body>
+</Note>
+<Note>
+	<Title type="bugfix">Helm chart schema type for nodeSelector was incorrect</Title>
+	<Body>
+The Helm chart schema for the `nodeSelector` value was incorrect. Kubernetes defines different types for nodeSelector (inside PodSpec objects) and NodeSelector (inside NodeAffinity, VolumeNodeAffinity and a bunch of other places). The schema was changed to use the correct type. The name `nodeSelector` is still used in the Helm chart so this change is backwards compatible.
+  </Body>
+</Note>
+<Note>
+	<Title type="bugfix">Pods with container ports named the same caused intercept to fail</Title>
+	<Body>
+Intercept container ports now have numbers appended to them if there are multiple ports from multiple containers with the same name. This bugfix works around an issue where Kubernetes allows multiple port definitions in a pod spec to have the same name.
+  </Body>
+</Note>
+<Note>
+	<Title type="bugfix">Don't include k8s-defs.json to chart package</Title>
+	<Body>
+The k8s-defs.json was unnecessarily included to the Helm chart package and this increased the Helm release secret size so much that it could prevent installation of the Helm chart depending on k8s settings. To fix this k8s-defs.json is not included to the Helm chart anymore.
+  </Body>
+</Note>
 ## Version 2.22.4 <span style={{fontSize:'16px'}}>(April 26)</span>
 <Note>
 	<Title type="bugfix">Don't require internet access when installing the traffic-manager using Helm</Title>
@@ -107,7 +133,7 @@ Key differences between `replace` and `intercept`:
 
 1. **Scope:** The `replace` command targets and affects an entire container, impacting all its traffic, while
    an `intercept` targets specific services and/or service/container ports.
-2. **Port Declarations:** Remote ports specified using the `--port` flag are container ports. 
+2. **Port Declarations:** Remote ports specified using the `--port` flag are container ports.
 3. **No Default Port:** A `replace` can occur without intercepting any ports.
 4. **Container State:** During a `replace`, the original container is no longer active within the cluster.
 

versioned_docs/version-2.22/variables.yml

@@ -1,2 +1,2 @@
-version: "2.22.4"
-dlVersion: "v2.22.4"
+version: "2.22.5"
+dlVersion: "v2.22.5"