adding breaking change information for orca

content/en/changelogs/1.36.0-changelog.md

@@ -42,8 +42,32 @@ controller:
 ```
 
 #### Orca
+#### Breaking Changes
+
+##### Front50 Timeout Configuration
+PR [#4773](https://github.com/spinnaker/orca/pull/4773) introduced a breaking change where timeouts were hardcoded at 10 seconds (readTimeoutMs: 10000, writeTimeoutMs: 10000, connectTimeoutMs: 10000), overriding global OkHttp timeout settings.
+
+The Kork global OkHttp defaults are:
+- connectTimeoutMs: 5000 (5 seconds)
+- readTimeoutMs: 120000 (120 seconds)
+- maxRequests: 100
+- maxRequestsPerHost: 100
+
+This hardcoding caused intermittent authentication failures during batch pipeline updates, especially with high latency or large pipeline configurations, as the global default read timeout of 120 seconds was being overridden with a much shorter 10 second timeout.
+
+If you're experiencing timeout issues, configure front50 timeouts explicitly to match or exceed your global OkHttp settings:
+
+```yaml
+front50:
+  okhttp:
+    readTimeoutMs: 120000  # Match Kork default
+    writeTimeoutMs: 120000  # Match read timeout
+    connectTimeoutMs: 5000  # Match Kork default
+```
+---------------------------------------------------
 Updates Orca's SavePipelineTask to support bulk saves using the updated functionality in the front50 bulk save endpoint.
 
+
 With https://github.com/spinnaker/orca/pull/4781, keys from the stage context's outputs section can now be removed (there by reducing the context size significantly).
 At present the following tasks support this feature:
 * PromoteManifestKatoOutputsTask