-
Notifications
You must be signed in to change notification settings - Fork 39k
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
Node Conformance Test: Statically link apiserver #30211
Node Conformance Test: Statically link apiserver #30211
Conversation
3d2b0d5
to
62dcd13
Compare
62dcd13
to
4143dbc
Compare
This PR is not for the master branch but does not have the |
lgtm |
feel free to mark this PR lgtm once the dependencies are merged. |
@vishh Thanks~ :) |
4143dbc
to
dd6584a
Compare
Just rebase, apply LGTM based on #30211 (comment) |
GCE e2e build/test passed for commit dd6584a. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit dd6584a. |
Automatic merge from submit-queue |
For #30122, #30174.
Based on #30116, #30198, #30200.
Please only review the 4th PR.
This PR is part of our roadmap to package node conformance test.
The 1st commit is from #30116, which started e2e services in a separate process.
The 2nd commit is from #30198, it statically linked etcd into the node e2e framework.
The 3rd commit is from #30200, it moved namespace controller into e2e services.
The 4th commit is new, it statically linked apiserver into the node e2e framework.
@dchen1107 @vishh
/cc @kubernetes/sig-node @kubernetes/sig-testing
This change is![Reviewable](https://camo.githubusercontent.com/2d899f4291d07d3cd2fa4aaae1e3b243f164c23fce87d30a589ace0d496a444c/68747470733a2f2f72657669657761626c652e6b756265726e657465732e696f2f7265766965775f627574746f6e2e737667)