317brian commented on code in PR #18919:
URL: https://github.com/apache/druid/pull/18919#discussion_r2748338628


##########
docs/release-info/release-notes.md:
##########
@@ -61,59 +61,282 @@ This section contains important information about new and 
existing features.
 
 This section contains detailed release notes separated by areas.
 
+#### Druid operator
+
+Druid Operator is a Kubernetes controller that manages the lifecycle of your 
Druid clusters. The operator simplifies the management of Druid clusters with 
its custom logic that is configurable through
+Kubernetes CRDs.
+
+[#18435](https://github.com/apache/druid/pull/18435)
+
+#### Cost-based autoscaling for streaming ingestion
+
+Druid now supports cost-based autoscaling for streaming ingestion that 
optimizes task count by balancing lag reduction against resource efficiency.. 
This autoscaling strategy uses the following formula:
+
+```
+totalCost = lagWeight × lagRecoveryTime + idleWeight × idlenessCost
+```
+
+which accounts for the time to clear the backlog and compute time:
+
+```
+lagRecoveryTime = aggregateLag / (taskCount × avgProcessingRate) — time to 
clear backlog
+idlenessCost = taskCount × taskDuration × predictedIdleRatio — wasted compute 
time
+```
+
+[#18819](https://github.com/apache/druid/pull/18819)
+
+#### Kubernetes client mode (experimental)
+
+THe new experimental Kubernetes client mode uses the `fabric8` 
`SharedInformers` to cache k8s metadata. This greatly reduces API traffic 
between the Overlord and k8s control plane. You can try out this feature using 
the following config:

Review Comment:
   ```suggestion
   The new experimental Kubernetes client mode uses the `fabric8` 
`SharedInformers` to cache k8s metadata. This greatly reduces API traffic 
between the Overlord and k8s control plane. You can try out this feature using 
the following config:
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to