Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feature: wait for APIExport to become available

Open
#37 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, kubernetes
Domain
api, backend

Research direction

Start by locating the agent’s handling of a missing APIExport during startup and trace how it reports the unavailable resource. Decide whether waiting is unconditional or controlled by a --wait-for-apiexport-exists flag; done means the agent no longer exits immediately when the source APIExport is absent and its behavior is covered by tests.

Written by the indexing model from the issue text.

Description

kind/feature
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?
  • I would like to work on this issue.
Additional Context

No response

Dominant language
Go
Stars
25
Forks
30
Avg merge
3d 9h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kcp-dev/api-syncagent

All issues in kcp-dev/api-syncagent

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.