Skip to content

Output dropped Creation/Update/Delete events when failed to sync Kong configuration by go-database-reconciler #7820

@randmonkey

Description

@randmonkey

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

In cases when error happens on syncing Kong configuration by GDR (For example, uploading configuration to KIC in Konnect CP), some events are dropped and not applied after error happen. To reduce the confusion, we should output the dropped events after bumping GDR version to include Kong/go-database-reconciler#362.

Proposed Solution

Collect dropped events from GDR and output them in either way (or both):

  • Add k8s events to related objects
  • Output them in logs

Additional information

The change should be released in patch of KIC 3.5 and KIC 3.4 LTS.

Acceptance Criteria

  • Users can knowt the events are dropped in syncing by either:
    • Events attached to related k8s resource
    • KIC logs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions