-
-
Notifications
You must be signed in to change notification settings - Fork 326
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
move kube -> kube-client and try to make a facade crate #652
Conversation
ok, everything is passing at least now so this is indeed viable. a bit of a faff internally with re-exporting features yet another time from the facade into kube into kube-core (and if we're coming from examples |
1345143
to
34420ea
Compare
Few things left:
Will try to finish the first 2 tomorrow. In the mean time, any quick look-overs of the new lib.rs examples and architecture.md would be appreciated. |
Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
also add a standalone readme Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]>
Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]>
so that we can use same paths equally depending on where we require them Signed-off-by: clux <[email protected]>
defaults to kube and will append ::core if kube or kube_client but users can also use it with kube_core directly Signed-off-by: clux <[email protected]>
they need to look like they came from the facade crate Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
…core` (#658) * Allow `#[derive(CustomResource)]` to take an arbitrary path to `kube_core` Signed-off-by: Teo Klestrup Röijezon <[email protected]> * Update kube-derive/src/lib.rs Co-authored-by: Eirik A <[email protected]> Co-authored-by: Eirik A <[email protected]> Signed-off-by: clux <[email protected]>
fa1ee36
to
293a11c
Compare
Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> minor doc improvements Signed-off-by: clux <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> Update examples/README.md Co-authored-by: kazk <[email protected]> Signed-off-by: clux <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]> Update architecture.md Co-authored-by: kazk <[email protected]>
Lovely how even trivial docs changes get tripped up by the DCO bot :/ On a more practical note, the constant force-pushing that this leads to is really annoying when trying to follow links from email notifications. |
Yeah, it's almost easier to search and replace doc changes yourself on this scale. Thankfully, it was time to do a rebase anyway. |
Ah, yeah, that is true. I tried to limit most the force pushing here to the very end, but maybe I should wait until PRs are complete ready to go / approved in the future (although then we have to deal with emails from failing DCO bot).. |
* add conditions::is_accepted for crds - closes #655 Signed-off-by: clux <[email protected]> * rename to established based on new information + timout guard Signed-off-by: clux <[email protected]> * simplify a bit Signed-off-by: clux <[email protected]> * traitify condition Signed-off-by: clux <[email protected]> * docs for Condition fn trait Signed-off-by: clux <[email protected]> * add example for await_condition as well Signed-off-by: clux <[email protected]> * fix pedantic lints Signed-off-by: clux <[email protected]>
I'm pretty happy with how documentation looks now all over. After the last cleanup in #662 is done, i'll probably want to merge both and do a release. Are we otherwise happy with this PR? Happy to spend some more time on it if there's something. |
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.
Looks good to me.
Have you tried using this branch from outside? I remember #525 (comment) worked fine in this workspace, but didn't outside. Just wanted to make sure we don't have anything like that.
Ah. That's a good point. I'll verify in controller-rs first. |
Ok. It does seem to work fine from controller-rs and version-rs, but going to hold off until tomorrow. Want to POC the |
ws = ["client", "tokio-tungstenite", "rand", "kube-core/ws"] | ||
oauth = ["client", "tame-oauth"] | ||
gzip = ["client", "tower-http/decompression-gzip"] | ||
client = ["config", "__non_core", "hyper", "http-body", "tower", "tower-http", "hyper-timeout", "pin-project", "chrono", "jsonpath_lib", "bytes", "futures", "tokio", "tokio-util", "either"] |
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.
What does it mean to build kube-client
without client
?
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.
you can still get the config
out of it. effectively it's similar to old kube
, but could possibly strip the kube-client
a bit more now.
Signed-off-by: clux <[email protected]>
- simpler names for snappier docs - removes client side validation - see #654 - everything in one file in root (200 lines after all) - avoids clippy lint Signed-off-by: clux <[email protected]>
Co-authored-by: Teo Klestrup Röijezon <[email protected]> Update architecture.md Co-authored-by: Teo Klestrup Röijezon <[email protected]> Update architecture.md Co-authored-by: Teo Klestrup Röijezon <[email protected]> Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
Signed-off-by: clux <[email protected]>
Bah. DCO bot is not super reliable in its suggestions for how to fix missing signoffs across big prs... Doing a big force push again. |
* add Resource::object_ref helper to simplify event recording Signed-off-by: clux <[email protected]> * a few more simplifications to events recorder Signed-off-by: clux <[email protected]> * fmt Signed-off-by: clux <[email protected]> * clippy + broken doc links Signed-off-by: clux <[email protected]> * one line clarification Signed-off-by: clux <[email protected]> * remove remnants of derive feature from kube-client Signed-off-by: clux <[email protected]> * only clone what is necessary Signed-off-by: clux <[email protected]> * code review doc comments Signed-off-by: clux <[email protected]> * 2021 edition (#664) Signed-off-by: clux <[email protected]>
Ok. Last tweak to events api + rust 2021 upgrade is in here. Will add CHANGELOG entries and release tonight if all goes as planned :-) |
quick play around with #651
kind of just moves kube the entire crate and avoids the error nesting problem by re-exporting
kube_client::Error
askube::Error
, not sure if that's the best solution. kind of delays the error story out further, but that's also good that we don't have to tackle it here.big changes are: