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
that mechanism for setting appropriate values in the object's status field automatically when a K8s Event with Warning severity is generated for such an object is only implemented for generated controllers with the helper EnsureProgrammedCondition.
Hence, for e.g. HTTPRoute in such a situation, something like this happens
having reason and status set to Unknown is not the best user experience. Even generic information is provided by the helper EnsureProgrammedCondition to check K8s Events generated for a respective object is much better user experience. e.g.
Proposed Solution
Adjust and reuse EnsureProgrammedCondition to provide properly set status for an object when a Warning K8s Event is registered for it. So for the example mentioned above instead of Unknown something like the below should be populated.
...
status:
conditions:
- lastTransitionTime: "2024-12-06T14:35:10Z"message: Object failed to be configured in Kong - see its attached Events formore information.observedGeneration: 1reason: Invalidstatus: "False"type: Programmed
It's a baseline and a nice default. Of course, having as detailed as possible statuses in addition to K8s Event makes KIC easier to use. Actual handling should be decided case by case.
Additional information
No response
Acceptance Criteria
For any configured K8s object, when a K8s Event with severity Warning is emitted, status is set accordingly as it happens for cgenerated controllersgenerated
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Does this enhancement require public documentation?
Problem Statement
Discovered during work on
that mechanism for setting appropriate values in the object's
status
field automatically when a K8sEvent
with Warning severity is generated for such an object is only implemented for generated controllers with the helper EnsureProgrammedCondition.Hence, for e.g.
HTTPRoute
in such a situation, something like this happenshaving
reason
andstatus
set toUnknown
is not the best user experience. Even generic information is provided by the helper EnsureProgrammedCondition to check K8sEvent
s generated for a respective object is much better user experience. e.g.Proposed Solution
Adjust and reuse EnsureProgrammedCondition to provide properly set status for an object when a Warning K8s
Event
is registered for it. So for the example mentioned above instead ofUnknown
something like the below should be populated.It's a baseline and a nice default. Of course, having as detailed as possible statuses in addition to K8s
Event
makes KIC easier to use. Actual handling should be decided case by case.Additional information
No response
Acceptance Criteria
Event
with severity Warning is emitted,status
is set accordingly as it happens for cgenerated controllersgeneratedThe text was updated successfully, but these errors were encountered: