You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#4932 aims at introducing the Accepted condition in the KongUpstreamPolicy object status. This issue is about adding the ancestor's programmed condition, which should be set after the clients push the configuration affected by the KongUpstreamPolicy to the dataplane.
Proposed Solution
When the client pushes a Service or a KongServiceFacade affected by a KongUpstreamPolicy, such an event is bubbled up to the controller, and the controller properly sets the ancestor's Programmed condition to True or False depending on the push outcome.
Additional information
No response
Acceptance Criteria
When a Service or a KongServiceFacade affected by a KongUpstreamPolicy is pushed, the ancestor status in the KongUpstreamPolicy gets updated according to the outcome of the push action.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem Statement
#4932 aims at introducing the
Accepted
condition in theKongUpstreamPolicy
object status. This issue is about adding the ancestor's programmed condition, which should be set after the clients push the configuration affected by theKongUpstreamPolicy
to the dataplane.Proposed Solution
When the client pushes a Service or a KongServiceFacade affected by a
KongUpstreamPolicy
, such an event is bubbled up to the controller, and the controller properly sets the ancestor'sProgrammed
condition toTrue
orFalse
depending on the push outcome.Additional information
No response
Acceptance Criteria
KongUpstreamPolicy
is pushed, the ancestor status in theKongUpstreamPolicy
gets updated according to the outcome of the push action.The text was updated successfully, but these errors were encountered: