Arko Dasgupta

raised https://github.com/kubernetes-sigs/gateway-api/issues/2826 in upstream

hey @TasdidurRahman ive started working on downstream mTLS https://github.com/envoyproxy/gateway/pull/2490 which is very similar to this PR, will try and wrap this up by this week, so this PR can reuse...

Sorry for the delay @TasdidurRahman , #2490 has merged, recommend using those helper xds methods for this PR as well, tia

Hey @TasdidurRahman can you rebase ?

@TasdidurRahman can you fix the lint errors, running `make lint` locally should highlight the errors

@TasdidurRahman all the conformance tests are failing, can you ptal

thanks for raising this issue, as of today there is no parent for any of the Policies, so every controller can reconcile it, which is the issue you are facing...

@zetaab we can't skip appending the policy into the result, since we need to have to update the status for all policies the solution here is some sort of partitioning,...

looks like there is a better solution upstream https://gateway-api.sigs.k8s.io/geps/gep-713/#standard-status-struct we'll need to replace the current status object https://github.com/envoyproxy/gateway/blob/a33c50582f7ff2ce19a64e8774905fe66b5a02bd/api/v1alpha1/securitypolicy_types.go#L34 with the upstream type https://github.com/kubernetes-sigs/gateway-api/blob/2ac95e4577ab9a0cedf9cc302f279f36aeb4d6db/apis/v1alpha2/policy_types.go#L187 this status is unique per controller (per...

> so basically the another controller is not responsible of that policy at all. So it should not be added as status we cannot determine why a controller reconciling a...