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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

temporarily pin clap and anstyle dependencies #190

Merged
merged 4 commits into from
Oct 20, 2023

Conversation

hawkw
Copy link
Collaborator

@hawkw hawkw commented Oct 16, 2023

This commit temporarily pins the clap dependency version to v4.3.24, since v4.4 changed Clap's MSRV to Rust 1.70, which our dev image doesn't have yet. It was also necessary to add an explicit dep on anstyle, a transitive dep via clap, so that we could pin that crate to v1.0.0, as v1.0.1 of anstyle also requires Rust 1.70.

@hawkw hawkw changed the title temporarily pin clap dependency temporarily pin clap and anstyle dependencies Oct 16, 2023
@hawkw
Copy link
Collaborator Author

hawkw commented Oct 16, 2023

lol, it looks like the tests also depend on regex_syntax which we also have to pin, i guess: https://github.com/olix0r/kubert/actions/runs/6538441492/job/17754360601?pr=190#step:8:16

@olix0r olix0r merged commit 7b47e77 into olix0r:main Oct 20, 2023
28 checks passed
hawkw added a commit that referenced this pull request Oct 20, 2023
Depends on #190 

Currently, Kubert has the option to use either Rustls or BoringSSL as
the TLS implementation. However, the BoringSSL feature is incomplete, as
it only configures Kubert's server to use BoringSSL, while the client
will still use "whatever `kube-client` is configured to use". This means
that you don't *really* get all-BoringSSL. Meanwhile, using BoringSSL on
the client-side is quite fraught without upstream support in
`kube-client`.

Therefore, this branch rips out the `boring-tls` feature and replaces it
with an `openssl-tls` feature. Now, we can ensure that the client and
server use the same TLS implementation, because `kube-client` already
supports OpenSSL. In addition, I've added new tests for the TLS server,
and changed the CI client tests to run with both TLS clients.

Closes #188
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants