-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Move hostPID tests to common #83368
Move hostPID tests to common #83368
Conversation
Hi @Jefftree. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@Jefftree: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @derekwaynecarr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
test/e2e/common/security_context.go
Outdated
} | ||
}) | ||
|
||
ginkgo.It("processes in containers sharing a pod namespace should be able to see each other [Alpha]", func() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/ this has been Beta since 1.12. Probably should remove the [Alpha]
tag. This also means we cannot make this a conformance test unless it gets promoted to GA in 1.17.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack. I searched through the codebase and didn't see a [Beta]
tag. Would that be unnecessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah
/assign |
5cccd1e
to
a750bf0
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're only trying to promote hostPID not shared PID namespace so I think you should reduce the scope of the PR
a750bf0
to
077e4b4
Compare
077e4b4
to
58e700c
Compare
/retest |
58e700c
to
20ac249
Compare
/retest |
/lgtm |
/assign @tallclair |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Jefftree, tallclair The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
These tests flaked on both GCE and kind in this PR and now they are flaking elsewhere :/ |
Some snippets from jobs failing return empty pid
return multiples pids
|
definitely flaking broadly, filed #84209 |
@Jefftree @tallclair can you open a revert to clear the queue while the flakiness is root caused? |
opened revert at #84212 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Move hostpid tests from
test/e2e_node
totest/e2e/common
. These tests should be eligible to be promoted to Conformance.Which issue(s) this PR fixes:
Fixes # #82547
Special notes for your reviewer:
These tests are a duplicate of the hostpid tests in
e2e_node
. I removed the check for shared pid namespace support (https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/security_context_test.go#L77) since it was only checking the Docker version (https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/docker_util.go#L53). Docker should not be an assumption we should be making about the container runtime.Does this PR introduce a user-facing change?:
/area conformance
/priority important-longterm
/ok-to-test
/sig node
/cc @johnbelamaric
/cc @tallclair