Open wmedlar opened 1 year ago
Hi, building for Darwin is intentionally not supported, as the EBS CSI Driver cannot run on Darwin. Building for Darwin should not be required to run the e2e tests (you will need to build for Linux, as the e2e tests must be run on a real cluster on AWS).
The e2e tests import code from the driver, which is why building on darwin is required. The driver itself and the resources created by the tests are all run in a real cluster. Like I mentioned in the original post, I don't have any interest in running the driver on darwin. I should, however, be able to run the e2e tests from my laptop without having to jump through hoops.
A stub implementation of the nodeService would be plenty fine, as would a clean separation between the application code and the e2e tests.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
/kind bug
What happened?
The project does not compile on MacOS / darwin because there is no code to implement the necessary
nodeService
methods like there is for Linux and Windows.What you expected to happen?
Code compiles well enough to run e2e tests.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?:
I don't actually want to run the driver on MacOS, but I do want to run e2e tests to validate my installation of the driver. Currently I can work around this by running the tests in a container.
Environment
kubectl version
): EKS 1.22