-
Notifications
You must be signed in to change notification settings - Fork 12
Introduce standalone SDK #60
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
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]
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.
Can we maybe add a quick markdown doc somewhere for the release process so that people tagging this repo are aware they need to tag both sdk and main module?
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
On-behalf-of: @SAP [email protected]
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: 63fe19c3155c710bab356f1208035a5fa6a8b929
|
|
[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 is exactly what kcp is also doing, declaring the SDK to be a standalone module to make it easier to import. I updated the codegen logic to "the best" kcp on kube 1.31 has to offer. Once kcp 0.28 is out, we can switch to kube_codegen.sh and cluster_codegen.sh and make it all silky smooth.
What Type of PR Is This?
/kind feature
Release Notes