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
Similarly to #3205, we'd like to make sure that all error/warnings detected by deck when applying configuration in DB-mode are properly propagated by means of Kubernetes events.
Proposed Solution
Refactor deck sync.Solver so it returns errors/warnings it detected.
Additional information
No response
Acceptance Criteria
When deck rejects an entity a Kubernetes Event is created on the resource that is the reason for rejection.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem Statement
Similarly to #3205, we'd like to make sure that all error/warnings detected by deck when applying configuration in DB-mode are properly propagated by means of Kubernetes events.
Proposed Solution
Refactor deck
sync.Solver
so it returns errors/warnings it detected.Additional information
No response
Acceptance Criteria
The text was updated successfully, but these errors were encountered: