v0.14.0 #1608
linkvt
announced in
Announcements
v0.14.0
#1608
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Breaking Changes
Interceptor timeout defaults changed (#1474)
Default timeout behavior has been redesigned.
KEDA_HTTP_REQUEST_TIMEOUTnow defaults to0(disabled),KEDA_HTTP_RESPONSE_HEADER_TIMEOUTdefaults to300s(was500ms), andKEDA_HTTP_READINESS_TIMEOUTdefaults to0(disabled, was20s). Timeout errors now return 504 instead of 502.The following environment variables have been removed:
KEDA_HTTP_TLS_HANDSHAKE_TIMEOUT,KEDA_HTTP_EXPECT_CONTINUE_TIMEOUT,KEDA_HTTP_KEEP_ALIVE,KEDA_HTTP_IDLE_CONN_TIMEOUT,KEDA_HTTP_DIAL_RETRY_TIMEOUT. These now use Go'sDefaultTransportdefaults.Interceptor metrics redesigned (#1563, #1590)
Metrics now use bounded labels:
path/hostreplaced byroute_name/route_namespace, and non-standard HTTP methods are normalized to_OTHER. Metrics have also been renamed to follow OTel semantic conventions:interceptor_requests_total→interceptor_request_count_total,interceptor_pending_requests→interceptor_request_concurrency. Dashboards must be updated.Highlights
New documentation (#1516)
The documentation has been completely rewritten and now lives at keda.sh/http-add-on. It features versioned docs, improved navigation, a quick start and guides for different personas (developers, cluster operators). The legacy in-repo docs have been removed.
InterceptorRoute CRD (#1532)
A new
InterceptorRouteCRD separates routing/interceptor configuration from scaling configuration.HTTPScaledObjectremains supported but is now deprecated — a warning is logged per resource to guide migration.See the user guide and the migration guide for details.
Per-route timeout configuration (#1562)
InterceptorRoute supports per-route timeouts via the
timeoutsspec withrequest,responseHeader, andreadinessfields. When unset, global env var defaults are used.Migration helper: orphan-scaledobject annotation (#1593)
The new
httpscaledobject.keda.sh/orphan-scaledobjectannotation lets you preserve the auto-created ScaledObject when deleting an HTTPScaledObject during migration to InterceptorRoute, avoiding scaling gaps.What's Changed
Full Changelog: v0.13.0...v0.14.0
Beta Was this translation helpful? Give feedback.
All reactions