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:
Patrick Ohly
2023-06-20 10:27:14 +02:00
parent 833156b77e
commit f2cfbf44b1
230 changed files with 834 additions and 680 deletions

View File

@@ -170,7 +170,7 @@ var _ = SIGDescribe("Kubelet Cgroup Manager", func() {
ginkgo.Describe("QOS containers", func() {
ginkgo.Context("On enabling QOS cgroup hierarchy", func() {
ginkgo.It("Top level QoS containers should have been created [NodeConformance]", func(ctx context.Context) {
f.It("Top level QoS containers should have been created", f.WithNodeConformance(), func(ctx context.Context) {
if !kubeletCfg.CgroupsPerQOS {
return
}
@@ -183,7 +183,7 @@ var _ = SIGDescribe("Kubelet Cgroup Manager", func() {
})
})
ginkgo.Describe("Pod containers [NodeConformance]", func() {
f.Describe("Pod containers", f.WithNodeConformance(), func() {
ginkgo.Context("On scheduling a Guaranteed Pod", func() {
ginkgo.It("Pod containers should have been created under the cgroup-root", func(ctx context.Context) {
if !kubeletCfg.CgroupsPerQOS {