-
Notifications
You must be signed in to change notification settings - Fork 12
Support APIExportEndpointSlices / kcp 0.28 #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/retest |
|
/retest |
1a48887 to
b0a948f
Compare
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
…te the AEES On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
b0a948f to
f3e6ee2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
LGTM label has been added. Git tree hash: 02a8f23513c0219049ab3b1204ad18b06735e37f
|
|
[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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
This implements support for APIExportEndpointSlices (AEES).
Starting with kcp 0.28, APIExports do not contain the virtual workspace URLs anymore (unless you specify a feature flag on kcp, and we certainly do not want to make that required for running the Agent). Instead in 0.28+, kcp will automatically create an AEES for each new APIExport, using the same name as the export.
In kcp 0.27, admins can manually create an AEES for their APIExport, but are not forced to because kcp still makes the URLs available in the APIExport.
To handle each and every situation, the agent now simply supports both scenarios. You can run it like before with
--apiexport-refif you're still on 0.27, or you can use--apiexportendpointslice-refwhen you are in kcp 0.28+ or you make use of custom AEES in 0.27 already. The agent'smainfunction will simply resolve the flags as before and figure it all out, so the main meat part of the agent can remain unchanged.What Type of PR Is This?
/kind feature
Related Issue(s)
Fixes #86
Release Notes