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
If the syncing APIExport is not available in the source cluster, api-syncagent exits immediately. This behavior breaks workflows where the user wants to start up pods / bins before creating APIExports.
Proposed Solution
Instead, the agent could wait indefinitely until the resource becomes available (maybe with a separate --wait-for-apiexport-exists flag).
Alternative Solutions
No response
Want to contribute?
I would like to work on this issue.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
I am not sure it's worth or wise to complicate the code with a wait loop. The agent is configured to sync a given APIExport, and this export doesn't exist. That is an (human) error and instead of hiding that in a silent forever-running wait loop, I much rather prefer the Pod to go into a CrashLoop, something that is detectable with monitoring tools like Prometheus.
Feature Description
If the syncing APIExport is not available in the source cluster, api-syncagent exits immediately. This behavior breaks workflows where the user wants to start up pods / bins before creating APIExports.
Proposed Solution
Instead, the agent could wait indefinitely until the resource becomes available (maybe with a separate
--wait-for-apiexport-exists
flag).Alternative Solutions
No response
Want to contribute?
Additional Context
No response
The text was updated successfully, but these errors were encountered: