Skip to content

feature: Support multiple API groups in one APIExport #47

@xrstf

Description

@xrstf

Feature Description

The agent was written under the (false?) assumption that 1 APIExport always contains exactly 1 APIGroup, and that the APIExport's name equals that api group. However this is supposedly not true.

Proposed Solution

The agent should be updated to not require a single API group, but to support multiple. It still will reconcile one single APIExport though.

Maybe there isn't even much to do, besides removing some validation.

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions