(Fixed in Apigee hybrid v1.8.5 and v1.9.1)
(Fixed in Apigee hybrid v1.9.1)Īdd support for Azure Front Door request headers to /healthz health check. (Fixed in Apigee hybrid v1.8.6)įixed an issue where in some circumstances the Java Callout would to fail due with the following error: Failed to execute JavaCallout. (Fixed in Apigee hybrid v1.7.6)įixed a conflict with an existing ASM on the cluster. The watcher component no longer fails when using Kubernetes Secret to store hybrid service account secret.
Note: Fixed in Apigee hybrid 1.8.4 and newer.
Requests failed with 500 response and error after upgrade to Hybrid 1.8. Please see Known issue 266452840 (Fixed in Apigee hybrid v1.7.6)įixed a narrow scenario where threads in runtime pods ended up consuming 100% CPU. In Apigee hybrid, fluentbit support now includes the NO_PROXY environment variable. MTLS-related client variables are now set by the Apigee runtime. (Fixed in Apigee hybrid v1.7.6 and v1.8.3) For more information, see pack_trace_reason in "UUID (proto)" in the envoy documentation. Note: This setting does have some impact on tracing in the ingress gateway.
The ingress gateway is now configured to consistently preserve UUID in the x-request-id header. (Fixed in Apigee hybrid v1.8.5 and v1.7.6)Īpigee Ingressgateway cannot access K8s secret from another namespace. You can now create a new environment with the same name as a deleted environment without needing to perform manual clean-up tasks first. Save money with our transparent approach to pricing Rapid Assessment & Migration Program (RAMP) Migrate from PaaS: Cloud Foundry, OpenshiftĬOVID-19 Solutions for the Healthcare Industry
0 kommentar(er)
