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/v1.15.4.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@
3
3
This update includes bug fixes:
4
4
5
5
-[Fix degradation of Workflow runtime performance over time](#fix-degradation-of-workflow-runtime-performance-over-time)
6
+
-[Allow Service Account for MetalBear mirrord operator in sidecar injector](#allow-service-account-for-metalbear-mirrord-operator-in-sidecar-injector)
6
7
7
8
## Fix degradation of Workflow runtime performance over time
8
9
@@ -23,3 +24,21 @@ This caused Jobs to fail, and enter failure policy retry loops.
23
24
### Solution
24
25
25
26
Refactor the Scheduler connection pool logic to properly prune stale connections to prevent job execution occurring on stale connections and causing failure policy loops.
27
+
28
+
## Allow Service Account for MetalBear mirrord operator in sidecar injector
29
+
30
+
### Problem
31
+
32
+
Mirrord Operator is not on the allow list of Service Accounts for the dapr sidecar injector.
33
+
34
+
### Impact
35
+
36
+
Running mirrord in `copy_target` mode would cause the pod to initalise with without the dapr container.
37
+
38
+
### Root cause
39
+
40
+
Mirrord Operator is not on the allow list of Service Accounts for the dapr sidecar injector.
41
+
42
+
### Solution
43
+
44
+
Add the Mirrord Operator into the allow list of Service Accounts for the dapr sidecar injector.
0 commit comments