k8s: Unify order of API server test cases

So far CIS-compliant configuration has been validated first unless
configuration used in ONAP release did not pass given benchmark.

Issue-ID: SECCOM-235
Change-Id: Ibdb523ab7ab6b8285757719721f75aca57beeb82
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>

diff --git a/test/security/k8s/src/check/validators/master/api_test.go b/test/security/k8s/src/check/validators/master/api_test.go
index 95b68da..ed93a5d 100644 (file)
--- a/test/security/k8s/src/check/validators/master/api_test.go
+++ b/test/security/k8s/src/check/validators/master/api_test.go
@@ -123,8 +123,8 @@ var _ = Describe("Api", func() {
                                Expect(IsSecurePortAbsentOrValid(params)).To(Equal(expected))
                        },
                        Entry("Is explicitly disabled on insecure cluster", []string{"--secure-port=0"}, false),
-                       Entry("Should be absent or set to valid port on Casablanca cluster", kubeApiServerCasablanca, true),
                        Entry("Should be absent or set to valid port on CIS-compliant cluster", kubeApiServerCISCompliant, true),
+                       Entry("Should be absent or set to valid port on Casablanca cluster", kubeApiServerCasablanca, true),
                )
 
                DescribeTable("Profiling",