Skip to content

Remove 1 APIExport = 1 API group limitation#52

Merged
kcp-ci-bot merged 4 commits into
mainfrom
multi-group
Apr 8, 2025
Merged

Remove 1 APIExport = 1 API group limitation#52
kcp-ci-bot merged 4 commits into
mainfrom
multi-group

Conversation

@xrstf

@xrstf xrstf commented Apr 8, 2025

Copy link
Copy Markdown
Contributor

Summary

When I begun workin with kcp, I was under the impression that an APIExport's name is always the API group for all resources it provides. That wasn't and isn't true though and you can easily have an APIExport named "foo" that contains "cronjobs.bar" and "databases.muh".

This PR cleans up the codebase a bit to remove any hints that the APIExport dictates the API groups.

Since the API group is now free, I added an option to also project it (i.e. rename foo.com to bar.com when transferring the CRDs).

Fixes #47.

What Type of PR Is This?

/kind feature

Release Notes

* The sync-agent does not mistakenly assume that 1 APIExport contains exactly 1 API group, and instead now correctly allows to have as many API groups as desired in one APIExport. You still need 1 agent per APIExport though.
* Added `group` to the projection settings in a PublishedResource, allowing to rewrite the API group.

xrstf added 4 commits April 8, 2025 14:03
On-behalf-of: @SAP christoph.mewes@sap.com
On-behalf-of: @SAP christoph.mewes@sap.com
On-behalf-of: @SAP christoph.mewes@sap.com
On-behalf-of: @SAP christoph.mewes@sap.com
@kcp-ci-bot kcp-ci-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Indicates the PR's author has signed the DCO. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 8, 2025
@xrstf xrstf requested a review from embik April 8, 2025 12:14

@embik embik left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2025
@kcp-ci-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 7f52b6a0e72dd0b2fba897edb758aa60ff0c5d91

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 8, 2025
@kcp-ci-bot kcp-ci-bot merged commit e6be33c into main Apr 8, 2025
@kcp-ci-bot kcp-ci-bot deleted the multi-group branch April 8, 2025 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature: Support multiple API groups in one APIExport

3 participants