Skip to content

Upgrade to kube-rs 0.75.0 #471

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

Closed
2 tasks done
nightkr opened this issue Sep 22, 2022 · 3 comments
Closed
2 tasks done

Upgrade to kube-rs 0.75.0 #471

nightkr opened this issue Sep 22, 2022 · 3 comments
Assignees

Comments

@nightkr
Copy link
Member

nightkr commented Sep 22, 2022

See https://github.com/kube-rs/kube-rs/releases/tag/0.75.0

I expect that kube-rs/kube#956 will require some type-level trickery to get around, but other than that it should be fairly smooth.

Ideally we don't introduce a breaking change in operator-rs if possible

  • kube-rs bumped to 0.75.0
  • If breaking change in operator-rs is made, release notes contain migration strategy
@nightkr nightkr moved this to Idea/Proposal in Stackable Engineering Sep 22, 2022
@lfrancke lfrancke moved this from Idea/Proposal to Refinement: Waiting for in Stackable Engineering Sep 27, 2022
@sbernauer sbernauer moved this from Refinement: Waiting for to Development: In Progress in Stackable Engineering Sep 27, 2022
@siegfriedweber siegfriedweber moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering Oct 10, 2022
nightkr added a commit that referenced this issue Oct 13, 2022
This is an alternate take on #481/#471 that does not introduce a new
operator-framework-level `Api` type. Instead, it introduces a new `GetApi`
trait that lets `Client::get_api` specialize as needed.
@nightkr nightkr linked a pull request Oct 13, 2022 that will close this issue
5 tasks
@nightkr nightkr moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Oct 14, 2022
bors bot pushed a commit that referenced this issue Oct 17, 2022
## Description

This is an alternate take on #481/#471 that does not introduce a new operator-framework-level `Api` type. Instead, it introduces a new `GetApi` trait that lets `Client::get_api` specialize as needed.



Co-authored-by: Teo Klestrup Röijezon <[email protected]>
@siegfriedweber siegfriedweber moved this to Development: Done in Stackable Engineering Oct 17, 2022
@lfrancke lfrancke moved this from Development: Done to Done in Stackable Engineering Oct 17, 2022
@sbernauer
Copy link
Member

@siegfriedweber what was the reason to reopen this ticket?

@siegfriedweber
Copy link
Member

The ticket was not yet approved in the acceptance stage. Now it is and can be closed finally.

@sbernauer
Copy link
Member

Ah sorry, didn't had a look at the Board stage....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment