e2e: use framework labels
This changes the text registration so that tags for which the framework has a dedicated API (features, feature gates, slow, serial, etc.) those APIs are used. Arbitrary, custom tags are still left in place for now.
This commit is contained in:
@@ -30,6 +30,7 @@ import (
|
||||
clientset "k8s.io/client-go/kubernetes"
|
||||
podutil "k8s.io/kubernetes/pkg/api/v1/pod"
|
||||
commonutils "k8s.io/kubernetes/test/e2e/common"
|
||||
"k8s.io/kubernetes/test/e2e/feature"
|
||||
"k8s.io/kubernetes/test/e2e/framework"
|
||||
e2eauth "k8s.io/kubernetes/test/e2e/framework/auth"
|
||||
e2ekubectl "k8s.io/kubernetes/test/e2e/framework/kubectl"
|
||||
@@ -45,7 +46,7 @@ const (
|
||||
serverStartTimeout = framework.PodStartTimeout + 3*time.Minute
|
||||
)
|
||||
|
||||
var _ = SIGDescribe("[Feature:Example]", func() {
|
||||
var _ = SIGDescribe(feature.Example, func() {
|
||||
f := framework.NewDefaultFramework("examples")
|
||||
f.NamespacePodSecurityLevel = admissionapi.LevelBaseline
|
||||
|
||||
|
Reference in New Issue
Block a user