Giter Site home page Giter Site logo

Comments (6)

erebe avatar erebe commented on July 4, 2024

Hello,

We are using this method in order to query the stats of the node directly.

let node_summary_request = Node::connect_get_proxy_with_path(node_name, "stats/summary", Default::default()).unwrap();

It seems this method have been removed by the change you describe.

Could you let me know if it is correct ? And if yes, if you see any alternative in the latest version to achieve this ?
At the moment, we pinned the version to v0.19.0 to avoid the breaking change.

Regards

from k8s-openapi.

Arnavion avatar Arnavion commented on July 4, 2024

Right, that is an API operation and so it has been removed. Also kube does not implement the full proxy API to .../proxy yet.

But since k8s-openapi never implemented the rest of the proxy response / stream handling, you presumably already have code to do that yourself. So you don't need support from kube for it anyway, just the http::Request that k8s-openapi used to give you. You can create it yourself as k8s-openapi used to: https://docs.rs/k8s-openapi/0.19.0/src/k8s_openapi/v1_27/api/core/v1/node.rs.html#178-199

from k8s-openapi.

erebe avatar erebe commented on July 4, 2024

Thank you for the swift answer @Arnavion.
Indeed, we have a custom parser for the raw bytes returned by this call.
We will try to use http::Request directly as you suggest :)

Thank you for Kube-rs

from k8s-openapi.

chubei avatar chubei commented on July 4, 2024

First of all thank you for your amazing work!

Responding to the comment request, we're using Pod::log_stream because Api::<Pod>::LogStream doesn't check (or expose) the status code of the HTTP response.

from k8s-openapi.

Arnavion avatar Arnavion commented on July 4, 2024

Yes, comparing Client::request_text (used by other CRUD API) with Client::request_stream (used by Pod::log_stream), the latter is missing the handle_api_errors or equivalent that would act on res.status(). Once it did that, that would solve the "check" problem, and it would also result in the status code appearing as Err(Error::Api(...)) which would solve the "expose" problem.

I didn't find an open issue on their tracker about this, so please open one and link it here.

from k8s-openapi.

chubei avatar chubei commented on July 4, 2024

Thanks for the research! Opened kube-rs/kube#1300.

from k8s-openapi.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.