Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: generate applyconfigurations for custom resources #217

Merged
merged 1 commit into from
Nov 10, 2023

Conversation

erikgb
Copy link
Contributor

@erikgb erikgb commented Oct 29, 2023

I think the migration to SSA in this project made the code harder to read/understand. 馃槈 While the support for SSA in the controller-runtime client is limited at present, ref. kubernetes-sigs/controller-runtime#347, I am convinced that we can do better.

Generating applyconfigurations with controller-gen is in the making, ref. kubernetes-sigs/controller-tools#818 and kubernetes-sigs/controller-tools#536, but it's a complex task that still needs some work.

In the meantime, I suggest generating applyconfigurations using the upstream generator that we can use in our controllers. I also suggest exporting the generated applyconfiguration types, even if I think client types should be available without depending on the operator module - creating a potential dependency-hell. This has been a long-standing issue in cert-manager that I hope can get some progress soon.

/cc @inteon @SgtCoDFish

@jetstack-bot jetstack-bot added dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Oct 29, 2023
@inteon
Copy link
Member

inteon commented Oct 29, 2023

/hold let's not merge this before the v0.7.0 release

@jetstack-bot jetstack-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Oct 29, 2023
@jetstack-bot jetstack-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 31, 2023
Signed-off-by: Erik Godding Boye <egboye@gmail.com>
@erikgb
Copy link
Contributor Author

erikgb commented Nov 7, 2023

The 0.7.0 release is history.

/unhold

@jetstack-bot jetstack-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 7, 2023
@erikgb
Copy link
Contributor Author

erikgb commented Nov 7, 2023

/retest

Copy link
Member

@SgtCoDFish SgtCoDFish left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

This doesn't seem to runtime impact currently - making it very easy to approve. Thanks for looking into this, I'm interested in following it!

@jetstack-bot jetstack-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 10, 2023
@jetstack-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SgtCoDFish

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jetstack-bot jetstack-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 10, 2023
@SgtCoDFish
Copy link
Member

/test pull-trust-manager-verify

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 that all commits in the pull request have the valid DCO sign-off message. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants