chore: upgrade api7 and gateway to v3.10.4 - #324
Conversation
Version bumps: - charts/api7: chart 3.10.2 -> 3.10.3, appVersion 3.10.4, and the dashboard / dp_manager / file_server / developer_portal image tags. - charts/gateway: chart 3.10.9 -> 3.10.10, appVersion 3.10.4, image tag. Structural changes synced from the products: - charts/gateway: new nginx.stream.realIpFrom, rendered as nginx_config.stream.real_ip_from. The gateway gained stream set_real_ip_from support in 3.10.4, so a gateway behind a load balancer that speaks the PROXY protocol on stream ports can see the real client address. The block is only rendered when the list is non-empty, matching the gateway default of trusting nobody. - charts/api7: extend the existing dashboard_configuration.console block with hybrid_mode, sentry and a commented custom_menu_group, mirroring control-plane helm/values.yaml. These now drive /api/fe-config, which 3.10.4 serves from the Go binary. - charts/api7: set database.max_lifetime to 1h for dashboard, dp_manager and developer_portal, replacing the commented 60s example. The control plane now bounds pooled connection lifetime by default so that connections pinned to a primary demoted by a failover are retired. READMEs regenerated with helm-docs; helm lint and helm template pass for both charts, with the stream real_ip_from block verified present only when nginx.stream.realIpFrom is set.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
2 participants
Chart release for API7 EE 3.10.4. 3.10 is the latest line, so this targets
main.Version bumps
charts/api7charts/gatewayImage tags move to
v3.10.4for dashboard, dp_manager, file_server and developer_portal, and to3.10.4for the gateway.Structural changes
charts/gateway— newnginx.stream.realIpFrom. The gateway gained streamset_real_ip_fromsupport in 3.10.4 (nginx_config.stream.real_ip_from, backed by--with-stream_realip_modulein apisix-runtime 1.3.11), so a gateway sitting behind a load balancer that speaks the PROXY protocol on stream ports can resolve the real client address instead of the directly connected peer. The chart rendersnginx_configexplicitly, so this needed a values field plus template rendering rather than passthrough. The block is emitted only when the list is non-empty, which matches the gateway's own default of trusting no address.charts/api7—console.*. 3.10.4 serves/api/fe-configfrom the Go binary, driven byconsole.*config keys. The existingdashboard_configuration.consoleblock (which already carriedaddr) is extended withhybrid_mode,sentryand a commentedcustom_menu_group, mirroringcontrol-planehelm/values.yamlverbatim.charts/api7—database.max_lifetime. The control plane now bounds pooled connection lifetime by default, so that connections pinned to a primary that a failover has demoted to read-only are eventually retired. The commented# max_lifetime: 60sexample is replaced with an explicitmax_lifetime: 1hfor dashboard, dp_manager and developer_portal, matching the control plane's own chart and its new default.Config keys that are not chart-exposed: the remaining gateway
config-default.yamldelta for this release is comment-only, and the control plane's other changes land in maps the chart already forwards withtoYaml.Validation
helm lint charts/api7 charts/gateway— 0 failed.helm templateon both charts renders the expected images (api7-ee-3-integrated:v3.10.4,api7-ee-dp-manager:v3.10.4,api7-ee-developer-portal:v3.10.4,api7-ee-3-gateway:3.10.4).stream:block by default, and present as a quoted list under--set nginx.stream.realIpFrom[0]=192.168.1.0/24.dashboard_configuration.consoleconfirmed to be a single key after the merge — the new keys extend the existing block instead of shadowingconsole.addr.make helm-docs.