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
Make Client configurable #540
Commits on Jun 3, 2021
-
Expose methods to configure TLS connection
- Add `Config::native_tls_connector` and `Config::rustls_client_config` - Remove the requirement of having `native-tls` or `rustls-tls` enabled when `client` is enabled. Allow one, both or none. - When both, the default Service will use `native-tls` because of kube-rs#153. `rustls` can be still used with a custom client. Users will have an option to configure TLS at runtime. - When none, HTTP connector is used. - Note that `oauth` feature still requires tls feature. - Remove tls features from kube-runtime
-
Depend on rustls directly instead of tokio-rustls
Still a dependency of hyper-rustls, but we're not using tokio-rustls. Depend on rustls directly instead.
-
-
-
Remove
client
fromnative-tls
andrust-tls
`config` + `native-tls`/`rustls-tls` can be used independently. For example, to create a simple HTTP client.
-
-
-
-
-
Relax Service's response body type
Allow using more from the Tower ecosystem.
-
-
Replace
LogRequest
layer withTraceLayer
Keeping this simple for now by default, but it's fully customizable.
-
-
Switch to custom tracing with callbacks
`kube=debug` can be used as before.
-
- Fix `http.url` - Remove unnecessary duration logs - Add `otel.kind` and `otel.status_code`
-
-
-
-
-
-
-
-
Commits on Jun 4, 2021
Commits on Jun 5, 2021
-
Add
client::ConfigExt
to extendConfig
forClient
- Move TLS methods to `ConfigExt` - Prepare to move `Auth` method to `ConfigExt` - `.option_layer(config.auth_layer()?)`
-
-
-
-
-
-
-
-
-