search

Kuadrant / architecture

Architecture Documents
0 stars 10 forks source link

Kuadrant Policies Status conditions/states #9

Closed didierofrivia closed 1 year ago

didierofrivia commented 1 year ago

This RFC presents 2 options and each one could be applied/develop in order and would reflect valuable and accurate information with different degrees of acuity. Given the feedback so far, it seems Option 2 is the winner:

Option 2 Based on GEP-713. In this case, besides the proposed Accepted PolicyType, the Enforced PolicyType would be added to reflect the final state of the policy, which means that the policy is showing the synced actual state of the Kuadrant services. The missing Failed PolicyType would be implicitly represented by the TargetNotFound and Invalid PolicyTypeReason.

Type Status Reason Message
Accepted True "Accepted" "KuadrantPolicy has been accepted"
False "Conflicted" "KuadrantPolicy is conflicted by [policy-ns/policy-name], ..."
False "Invalid" "KuadrantPolicy is invalid"
False "TargetNotFound" "KuadrantPolicy target [resource-name] was not found"
Enforced True "Enforced" "KuadrantPolicy has been successfully enforced"
False "PartiallyEnforced" "KuadrantPolicy has encountered some issues and has been partially applied"
False "Overridden" "KuadrantPolicy is overridden by [policy-ns/policy-name], ..."
maleck13 commented 1 year ago

I also wonder if perhaps this should be rolled into RLP v2? @guicassolato

alexsnaps commented 1 year ago

what are we doing with older RFCs like this, do we leave them open, is it still relevant?

We discussed this in last week's planning meeting, we need to do a "update" pass on this one. Make sure all is still in alignment with the v2 policy efforts…

maleck13 commented 1 year ago

@didierofrivia this section of the policy attachment gep may be relevant https://gateway-api.sigs.k8s.io/geps/gep-713/#conditions