osm icon indicating copy to clipboard operation
osm copied to clipboard

Handle/record errors and events for webhooks and other components

Open jsturtevant opened this issue 3 years ago • 2 comments

Please describe the Improvement and/or Feature Request

Should consider consistent approach to raising events for errors and other major events that happen in the system.

Scope (please mark with X where applicable)

  • New Functionality [ ]
  • Install [ ]
  • SMI Traffic Access Policy [ ]
  • SMI Traffic Specs Policy [ ]
  • SMI Traffic Split Policy [ ]
  • Permissive Traffic Policy [ ]
  • Ingress [ ]
  • Egress [ ]
  • Envoy Control Plane [ ]
  • CLI Tool [ ]
  • Metrics [ ]
  • Certificate Management [ ]
  • Sidecar Injection [ ]
  • Logging [ ]
  • Debugging [ ]
  • Tests [ ]
  • CI System [ ]
  • Demo [ ]
  • Project Release [ ]

Possible use cases

An example would be when a webhook is rotating its certificate. How does an end user identify that this failed? Currently can be identified by looking at the logs. If we raise events on major events a user could use something like kubectl describe deployment <webhook> which would include an event that it failed. This would allow events to be tied into other systems.

jsturtevant avatar Aug 01 '22 18:08 jsturtevant

Added default label size/needed. Please consider re-labeling this issue appropriately.

github-actions[bot] avatar Sep 08 '22 00:09 github-actions[bot]

Added default label kind/needed. Please consider re-labeling this issue appropriately.

github-actions[bot] avatar Sep 08 '22 00:09 github-actions[bot]