Dynamic batching requests for Executors were not working when using docarray>=0.30.0. This fix makes this feature fully compatible with newer versions of DocArray.
Monitoring validation error with docarray>=0.30 (#5965)
When using docarray>=0.30 in combination with monitoring, there was a risk of getting a validation error because the input and output schemas were not properly considered.
Fail fast when no valid schemas (#5962)
When no valid schemas were used, Executors sometimes failed to load, but the Gateway would continue to try getting the endpoints from them until it timed out. Now, everything will stop faster without the long wait.
Properly handle multiprotocol Deployments to Kubernetes (#5961)
When converting a Deployment using multiple protocols to Kubernetes YAML, the resulting services did not use or expose the ports and protocols as expected. This has now been fixed.
Fix gRPC connectivity issues for health check (#5972)
Fixed issues for Flow not being able to health-check Executors due to HTTP proxy used.
Now this is changed, and when doing:
from jina import Deployment
d = Deployment(protocol=['grpc', 'http'])
d.to_kubernetes_yaml('./k8s-deployment')
You will get a YAML where the two services expose each protocol.
🤟 Contributors
We would like to thank all contributors to this release:
Release Note
This release contains 5 bug fixes.
🐞 Bug Fixes
Dynamic batching with docarray>=0.30 (#5970)
Dynamic batching requests for Executors were not working when using docarray>=0.30.0. This fix makes this feature fully compatible with newer versions of DocArray.
Monitoring validation error with docarray>=0.30 (#5965)
When using docarray>=0.30 in combination with monitoring, there was a risk of getting a validation error because the input and output schemas were not properly considered.
Fail fast when no valid schemas (#5962)
When no valid schemas were used, Executors sometimes failed to load, but the Gateway would continue to try getting the endpoints from them until it timed out. Now, everything will stop faster without the long wait.
Properly handle multiprotocol Deployments to Kubernetes (#5961)
When converting a
Deploymentusing multiple protocols to Kubernetes YAML, the resulting services did not use or expose the ports and protocols as expected. This has now been fixed.Fix gRPC connectivity issues for health check (#5972)
Fixed issues for Flow not being able to health-check Executors due to HTTP proxy used.
Now this is changed, and when doing:
You will get a YAML where the two services expose each protocol.
🤟 Contributors
We would like to thank all contributors to this release: