![]() Automatic merge from submit-queue (batch tested with PRs 67071, 66906, 66722, 67276, 67039). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Promoting "[sig-storage] Secrets should be able to mount in a volume regardless of a different secret existing with same name in different namespace" to Conformance **What this PR does / why we need it**: An consolidated effort to resolve the issue https://github.com/kubernetes/kubernetes/issues/66875 > _[sig-storage] Secrets should be able to mount in a volume regardless of a different secret existing with same name in different namespace_ Promoting mentioned e2e test for Conformance as it - - Validates that secret with same name can be created in different namespaces but secrets which reside in same namespace as that of pod can be only be accessed from volume mounted in the container. - Improves api coverage including prioritized Pod API lists. https://github.com/cncf/k8s-conformance/issues/220#issuecomment-393344061 > GET /api/v1/namespaces/{namespace}/pods/{name}/log GET /api/v1/namespaces/{namespace}/pods GET /api/v1/namespaces/{namespace}/pods/{name} POST /api/v1/namespaces/{namespace}/pods PUT /api/v1/namespaces/{namespace}/pods/{name}/status DELETE /api/v1/namespaces/{namespace}/pods DELETE /api/v1/namespaces/{namespace}/pods/{name} **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes # **Special notes for your reviewer**: No Flakes Found. ``` • [SLOW TEST:16.326 seconds] [sig-storage] Secrets /home/vagrant/go-workspace/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/secrets_volume.go:33 should be able to mount in a volume regardless of a different secret existing with same name in different namespace [NodeConformance] /home/vagrant/go-workspace/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/secrets_volume.go:86 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS Aug 7 07:12:44.133: INFO: Running AfterSuite actions on all node Aug 7 07:12:44.134: INFO: Running AfterSuite actions on node 1 Ran 1 of 1020 Specs in 16.441 seconds SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 1019 Skipped PASS All tests passed... Will keep running them until they fail. This was attempt #40 No, seriously... you can probably stop now. ``` **Release note**: ```release-note NONE ``` /area conformance @kubernetes/sig-node-pr-reviews |
||
---|---|---|
.. | ||
testdata | ||
BUILD | ||
cf_header.md | ||
conformance_test.sh | ||
OWNERS | ||
README.md | ||
walk_test.go | ||
walk.go |
This directory contains the regression test for controlling the list of all conformance tests.
If you add or remove a conformance test, this test will fail and you will need
to update the golden list of tests stored in testdata/
. Changes to that file
require review by sig-architecture.
To update the list, run
$ bazel build //test/conformance:list_conformance_tests
$ cp bazel-genfiles/test/conformance/conformance.txt test/conformance/testdata
Add the changed file to your PR, then send for review.