List applying policies in mt-brokers .status.policies

[creydr]

As the Eventing Authorization feature track describes, target resources of EventPolicies, will reflect in their status, which EventPolicy is applied to them.

For example:

apiVersion: eventing.knative.dev/v1
kind: Broker
metadata:
  name: my-broker
spec:
  ...
status:
  ...
  policies:
    - name: event-policy
      apiVersion: v1alpha1
    - name: another-event-policy
      apiVersion: v1alpha1

  conditions:
    - type: Ready
      status: "True"
    - type: EventPoliciesReady
      status: "True"

As the mt-broker should support EventPolicies, wee need to do the following:

• Update the Broker reconciler to show applying policies in the Brokers .status.policies and set the Brokers EventPoliciesReady condition. Also watch EventPolicies for changes.
• Set EventPoliciesReady condition to true, in case no policy applies, and set message according to the default-authorization-mode (e.g. Default authorization mode is 'allow-all'). Check the Default Authorization Mode section in the feature track for additional information.

Hint:

• Adding AppliedEventPoliciesStatus to the Broker is done in Add AppliedEventPoliciesStatus type #7975

Prerequisites:

• Add Library to support on AuthZ #7985
• Add AppliedEventPoliciesStatus type #7975

Additional hints for new contributors before starting with this issue:

1. When the issue has the Draft status, the issue is subject to change and thus should not be started to be worked on
2. Make sure you've read and understood the CONTRIBUTING.md guidelines
3. Make sure you're able to run Knative Eventing locally and run at least the unit tests.
4. Feel free to raise any questions you have either directly here in the issue, in the #knative-eventing Slack channel or join the Eventing Workgroup Meeting
5. When you feel comfortable with this issue, feel free to assign it to you (e.g. by commenting /assign). Please be aware that we might unassign you, if we don't see any progress from your side to give other contributors also a chance to work on this issue.

[asr2003]

/assign

[EraKin575]

@asr2003 are you still working on this issue?

[creydr]

@asr2003 are you still working on this issue?

@EraKin575, this issue is still in status "Backlog", as not all the dependent issues (e.g. #7985 (which should be done soon)) are resolved yet. So @asr2003 didn't have a chance to work on it yet.

[asr2003]

Yes, waiting to solve upstream issue

…

On Mon, 17 Jun, 2024, 5:08 pm Christoph Stäbler, ***@***.***> wrote: @asr2003 <https://github.com/asr2003> are you still working on this issue? @EraKin575 <https://github.com/EraKin575>, this issue is still in status "Backlog", as not all the dependent issues (e.g. #7985 <#7985> (which should be done soon)) are resolved yet. So @asr2003 <https://github.com/asr2003> didn't have a chance to work on it yet. — Reply to this email directly, view it on GitHub <#7976 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGXZB6GJH5EGZX2YDZ4XPHDZH3DCFAVCNFSM6AAAAABJB2H6HGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZTGE2TINJQGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[creydr]

Hey @asr2003,
This issue is ready to be worked on. You can also check on #8014, how we solved this for the Channel (particularly on b7ff773 and 7891138).
Please let us know if you have any questions :)

[asr2003]

Yeah! Thanks, will fix soon. I have ongoing exams now. Will submit a PR within a week :)

…

On Mon, 24 Jun, 2024, 8:29 pm Christoph Stäbler, ***@***.***> wrote: Hey @asr2003 <https://github.com/asr2003>, This issue is ready to be worked on. You can also check on #8014 <#8014>, how we solved this for the Channel (particularly on b7ff773 <b7ff773> and 7891138 <7891138> ). Please let us know if you have any questions :) — Reply to this email directly, view it on GitHub <#7976 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGXZB6FS2FKROCWQQKZBXZLZJAX5FAVCNFSM6AAAAABJB2H6HGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWG44DKNJSGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[creydr]

Hello @asr2003,
Good luck with your exams 🤞
As this issue in in iteration 2 which ends next week (July 6th), please let us know if you'll be able to finish it till then (please also count some time for review cycles).
Please don't feel stressed about it with your exams and feel free to otherwise unassign yourself, so that another contributor could pick this up.

[asr2003]

@creydr Will unassign this and will reassign if any other contributor not pickup the issue till my exams are done