Spring Boot 2.3.1.RELEASE Reference Documentation depending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 535 页 | 11.58 MB | 1 年前3- Spring Boot 2.3.10.RELEASE Reference Documentation depending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 549 页 | 11.77 MB | 1 年前3
- Spring Boot 2.3.9.RELEASE Reference Documentation depending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 548 页 | 11.77 MB | 1 年前3
- Spring Boot 2.3.0.M4 Reference Documentation depending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 537 页 | 11.55 MB | 1 年前3
- Spring Boot 2.3.6.RELEASE Reference Guidedepending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 543 页 | 11.71 MB | 1 年前3
- Spring Boot 2.4.0-M1 Reference Guidedepending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 539 页 | 11.61 MB | 1 年前3
- Spring Boot 2.3.8.RELEASE Reference Guidedepending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 546 页 | 11.75 MB | 1 年前3
- Spring Boot 2.5.13 Reference Documentation depending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 702 页 | 13.82 MB | 1 年前3
- Spring Boot 2.4.x-SNAPSHOT Reference Documentationdepending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 650 页 | 13.12 MB | 1 年前3
- Spring Boot 2.5.3 Reference Documentationdepending on the provider. A Service that has an explicit Ingress will also respond in a way that depends on the implementation - the ingress service itself will have to decide how to handle the "connection "connection refused" from downstream. HTTP 503 is quite likely in the case of both load balancer and ingress. Also, if an application is using Kubernetes autoscaling it may react differently to applications0 码力 | 692 页 | 13.67 MB | 1 年前3
共 76 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8