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
{{ message }}
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.
One of those status conditions is the Ready condition which is already present in TLSPolicy.
But we want to add a new condition Accepted this is in affect that the controller has validated that the policy is correct and valid and ready to be acted on. Things that may cause this not to be the case
TLSPolicy targeting a non gateway resource
TLSPolicy targeting a resource that has been deleted or not found
Another TLSPolicy being present and targeting the same ref
Done
Add logic to validate and calculate the correct Accepted condition in the TLSPolicy controller based on the RFC
What
Based on https://github.com/Kuadrant/architecture/blob/main/rfcs/0004-policy-status.md we want to have some consistent status in place.
One of those status conditions is the
Ready
condition which is already present in TLSPolicy.But we want to add a new condition
Accepted
this is in affect that the controller has validated that the policy is correct and valid and ready to be acted on. Things that may cause this not to be the caseDone
The text was updated successfully, but these errors were encountered: