dream11 / kong-circuit-breaker Goto Github PK

Summary

kong-circuit-breaker does not work along OAuth2 kong plugin. Paths where OAuth2 its set, kong-circuit-breaker api_call_timeout_ms` does not apply

Steps To Reproduce

1. Install OAuth2 plugin at a service
2. Install kong-circuit-breaker plugin

Additional Details & Logs

• Kong version Kong Enterprise 2.7.0.0

Summary

I have an API endpoint as follows: https://test-cb.example.com/kong-circuit-breaker/api/v2/<-user-id-as-a-path-variable->
and I have an ingress for this endpoint as mentioned below:

kind: Ingress
apiVersion: extensions/v1beta1
metadata:
  name: test-ingress
  namespace: stage
  annotations:
    konghq.com/plugins: circuit-breaker-stage
spec:
  ingressClassName: kong-internal
  tls:
    - hosts:
        - test-cb.example.com
  rules:
    - host: test-cb.example.com
      http:
        paths:
          - path: /kong-circuit-breaker/api/v2/
            pathType: ImplementationSpecific
            backend:
              serviceName: stage-user-service
              servicePort: 80

and circuit-breaker config as below:

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  namespace: stage
  name: circuit-breaker-stage
config:
  window_time: 30
  api_call_timeout_ms: 2000
  min_calls_in_window: 10
  failure_percent_threshold: 51
  wait_duration_in_open_state: 60
  wait_duration_in_half_open_state: 90
  half_open_min_calls_in_window: 5
  half_open_max_calls_in_window: 10
  error_status_code: 599
  excluded_apis: '{"GET_/kong-circuit-breaker/actuator/health": true}'
plugin: circuit-breaker

I'm have added kong-circuit-breaker for the above route and tried testing it and found out that each request URL for this route is having independent circuit-breaker state maintained where my expectation was that single circuit breaker state will be maintained for the route/routes configured in ingress instead for each request URL.

Is there a way to specify in kong-circuit-breaker to maintain the state of circuit-breaker for aggregated count of all the requests made to the API with the path specified in Ingress.

Example: Irrespective of user-Id in the following path: kong-circuit-breaker/api/v2/<-user-id-as-a-path-variable->, the circuit-breaker should open, if the failure percentage reaches the threshold for this API.
Whereas the current behaviour is that the circuit-breaker for the API with path: kong-circuit-breaker/api/v2/adam123 is open, while the same API with path: kong-circuit-breaker/api/v2/maria456 is allowing the requests to the service.

PS: I'm not sure if this issue has to be submitted as a bug or feature request.

Thanks.

Summary

This action increases the version of dependencies also in the rockspec file if the version coincides with the version of the plugin

Steps To Reproduce

1. Check this commit

Summary

If a timeout is triggered，when I disabled this plugin，it also say "The upstream server is timing out".
Very urgent

Steps To Reproduce

Additional Details & Logs

• Kong version ($ kong 2.4.1)
• Kong debug-level startup logs ($ kong start --vv)
• Kong error logs (<KONG_PREFIX>/logs/error.log)
• Kong configuration (the output of a GET request to Kong's Admin port - see
  https://docs.konghq.com/latest/admin-api/#retrieve-node-information)