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
The policy-controller performs periodic reconciliation of HTTPRoute statuses.
This logic is supposed to only perform a PATCH when the desired .status.parents != the actual .status.parents.
The logic used to compare the desired and actual state is order-dependent. Thus if statuses from other controllers aren't in the order Linkerd expects, it will PATCH the HTTPRoute.
This isn't the desired behavior, since the order of elements elements in .status.parents doesn't matter.
How can it be reproduced?
I have a unit test in the attached PR that reproduces this issue.
Logs, error output, etc
N/A
output of linkerd check -o short
N/A
Environment
Kubernetes: 1.28
Linkerd: Master
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered:
What is the issue?
policy-controller
performs periodic reconciliation ofHTTPRoute
statuses.PATCH
when the desired.status.parents
!= the actual.status.parents
.PATCH
theHTTPRoute
..status.parents
doesn't matter.How can it be reproduced?
Logs, error output, etc
N/A
output of
linkerd check -o short
N/A
Environment
Kubernetes: 1.28
Linkerd: Master
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered: