docs: add manual Istio sidecar update instructions for v4.7.0 or higher (#122)

Author: CasLubbers

.cspell.json

@@ -108,7 +108,8 @@
     "uxqf",
     "xvjf",
     "initdb",
-    "creds"
+    "creds",
+    "proxyv"
   ],
   "language": "en",
   "words": [

docs/for-ops/upgrade-notes.md

@@ -8,6 +8,65 @@ sidebar_label: Upgrade Notes
 
 In some cases between versions upgrades there are issues that can occur, on this page you will find fixes on how to deal with those issues.
 
+## v4.7.0
+
+### Manual Istio Sidecar Updates Required
+
+Due to an issue with automatic Istio sidecar restarts for certain pod types, manual intervention is required after upgrading Istio to ensure all pods have the latest sidecar version.
+
+#### Affected Pod Types
+
+The following pod types require manual restart after Istio upgrades:
+
+1. TTY pods (standalone pods without controllers)
+2. Tekton EventListener pods (managed by Tekton controllers)
+
+#### Manual Restart Procedures
+
+**For TTY Pods:**
+
+TTY pods are standalone and will not be recreated automatically when deleted. Handle with care:
+
+```shell
+# Delete all TTY pods (WARNING: This will terminate TTY sessions for any connected users)
+kubectl delete pods -A -l otomi=tty
+```
+
+:::warning
+Deleting TTY pods will disconnect any active user sessions and the pods will NOT be recreated automatically. Users will need to create a new TTY session through the UI. Coordinate with users before performing this action.
+:::
+
+**For Tekton EventListener Pods:**
+
+EventListener pods will be automatically recreated by the Tekton controller:
+
+```shell
+# Delete all EventListener pods (safe - will be recreated automatically)
+kubectl delete pods -A -l app.kubernetes.io/managed-by=EventListener
+```
+
+:::note
+The Tekton controller will automatically recreate the pod with the new Istio sidecar.
+:::
+
+#### Verification
+
+After restarting pods, verify they have the correct Istio sidecar version:
+
+```shell
+# Get the current Istio version for comparison
+echo "=== Current Istio Version ==="
+kubectl get deployment -n istio-system -l app=istiod -o jsonpath='{.items[0].spec.template.spec.containers[0].image}' | cut -d: -f2
+
+echo ""
+echo "=== TTY Pods Sidecar Versions ==="
+kubectl get pods -A -l otomi=tty -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.spec.containers[?(@.image contains "istio/proxyv2")].image}{"\n"}{end}' | column -t
+
+echo ""
+echo "=== EventListener Pods Sidecar Versions ==="
+kubectl get pods -A -l app.kubernetes.io/managed-by=EventListener -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.spec.containers[?(@.image contains "istio/proxyv2")].image}{"\n"}{end}' | column -t
+```
+
 ## v4.4.4 to v4.7.0 or higher
 
 From v4.4.4 to a higher version there might occur an issue with the harbor redis, which results in the harbor-redis-0 pod restarting indefinitely.