Retry mechanism for pubsub

open-policy-agent / gatekeeper

🐊 Gatekeeper - Policy Controller for Kubernetes

https://open-policy-agent.github.io/gatekeeper/

Apache License 2.0

3.72k stars 764 forks source link

Retry mechanism for pubsub #2889

Open JaydipGabani opened 1 year ago

JaydipGabani commented 1 year ago

Describe the solution you'd like [A clear and concise description of what you want to happen.] Audit prevents publishing a violation if it fails on the first try. It would be helpful to have some sort of retry mechanism to make sure we do not move on after just one publishing try in the event of an error.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] The following questions might help in understanding some of the requirement:

Can we rely on retry logic on the underlying pub sub tool?
Should the driver implement this logic of retry?
How to make the retries configurable? (pass it in connection client config?)

Environment:

Gatekeeper version:
Kubernetes version: (use kubectl version):

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

maxsmythe commented 1 year ago

Are we still working on pubsub?

JaydipGabani commented 1 year ago

Not working actively on this issue, but we can keep it open and see if ppl want this or not maybe?

stale[bot] commented 12 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

JaydipGabani commented 12 months ago

Keep this open

stale[bot] commented 10 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

stale[bot] commented 8 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

stale[bot] commented 5 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

stale[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.