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
When KongUpstreamPolicy is attached to an object (Service or GW API *Route) using the konghq.com/upstream-policy, the controller should populate its status accordingly:
When Service is annotated and used in GW API rule with multiple backend refs, but their konghq.com/upstream-policy annotations do not match, status.ancestors is populated with Accepted condition with status Conflicted
The condition Accepted is set with Value "True" and Reason=Accepted if Service is annotated and the above condition does not happen
Ensure that envtests covering the controller are added that will mock successful config update and will ensure that conditions are properly populated.
Proposed solution
A new controller watches KongUpstreamPolicy, Service, and *Routes and set the KongUpstreamPolicy status according to the above rules.
Acceptance criteria
status.ancestors slice is populated with one entry per each KongUpstreamPolicy-associated object
The text was updated successfully, but these errors were encountered:
Problem Statement
When
KongUpstreamPolicy
is attached to an object (Service or GW API *Route) using thekonghq.com/upstream-policy
, the controller should populate its status accordingly:konghq.com/upstream-policy
annotations do not match,status.ancestors
is populated withAccepted
condition with statusConflicted
Accepted
is set with Value "True" andReason=Accepted
if Service is annotated and the above condition does not happenEnsure that envtests covering the controller are added that will mock successful config update and will ensure that conditions are properly populated.
Proposed solution
A new controller watches
KongUpstreamPolicy
,Service
, and*Route
s and set theKongUpstreamPolicy
status according to the above rules.Acceptance criteria
status.ancestors
slice is populated with one entry per eachKongUpstreamPolicy
-associated objectThe text was updated successfully, but these errors were encountered: