-
Notifications
You must be signed in to change notification settings - Fork 39
-
Notifications
You must be signed in to change notification settings - Fork 39
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
has someone gotten k3s
to work?
#200
Comments
Hi @bbortt 👋 It works in our test-suite at least 🤔 |
@DDtKey thanks for the quick response. I saw that the test suite works and I can reproduce that. but it does only read pods, not create any new.. as soon as I go into this direction I end up with the mentioned error.. [dev-dependencies]
assert_cmd = "2.0.16"
k8s-openapi = { version = "0.22.0", features = ["latest"] }
kube = { version = "0.93.1", features = ["derive"] }
kube-derive = "0.93.1"
predicates = "3.1.2"
rustls = "0.23.12"
schemars = "0.8.21"
testcontainers-modules = { version = "0.9.0", features = [ "hashicorp_vault", "postgres"] } |
I guess you've figured out the reason and described in #202 Let me know if you have any questions. Thank you! |
not exactly, that was to build this community modules project locally. sorry if I was not specific enough. the build of the provided test still does not pass :/ tho not with the error I'd expect. |
example using the k8s pod api. also showcases running multiple k3s tests is only possible in serial (see `serial_test` crate).
example using the k8s pod api. also showcases running multiple k3s tests is only possible in serial (see `serial_test` crate).
Feature request description
I am trying to deploy a pod into
k3s
. I've followed the contained test (roughly), but fail to get it working. I've also considered thepod_api.rs
example over atkube-rs/kube
.has someone gotten this to work? I always end up with:
Service(hyper_util::client::legacy::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))
.this happens to be thrown in the
pods.create
line:Image reference
k3s
featureThe text was updated successfully, but these errors were encountered: