Added a cilium-bsc# test

config.json

@@ -0,0 +1,3 @@
+{
+"ClusterDir": "/Users/alexeitighineanu/go/src/github.com/fgerling/bdd-poc/imba-cluster"
+}

features/cilium/cilium-01.feature

@@ -0,0 +1,94 @@
+# doc1:   https://gitlab.suse.de/mkravec/scripts/blob/master/tests/cilium.sh
+# doc2:   http://docs.cilium.io/en/v1.6/gettingstarted/http/
+# TC:   https://github.com/fgerling/bdd-poc
+# This is a basic test for cilium (no PR or BSC provided)
+
+Feature: cilium-basic
+
+ Scenario: Test-Cilium-Basic on Skuba Cluster
+    Given "skuba" exist in gopath
+    And VARIABLE "work-folder" I get from CONFIG
+    When I run "skuba cluster status" in VAR:"work-folder" directory      
+    Then the output contains "master" and "worker"
+    When I run "kubectl get all --namespace=kube-system"
+    Then the output contains "cilium" and "dex"
+
+    Scenario: Deploy the starwars cilium pods
+    When I run "kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.6/examples/minikube/http-sw-app.yaml"
+    And wait "10 seconds"
+    When I run "kubectl get pods --selector=org=empire" 
+    Then the output contains "deathstar" and "tiefighter"
+    When I run "kubectl get pods --selector=org=alliance"
+    Then the output contains "xwing"
+
+    Scenario: Check the starwars cilium pods
+    When I run "kubectl get pods"                  
+    And grep for "xwing"
+    Then the output contains "running"
+    And grep for "deathstar"
+    Then the output contains "running"
+    And grep for "tiefighter"
+    Then the output contains "running"
+
+    Scenario: Test number1 if empire's ship is allowed into empire space
+    And I run "kubectl exec tiefighter -- curl -sm10 -XPOST deathstar.default.svc.cluster.local/v1/request-landing"
+    And wait "5 seconds"
+    Then the output contains "ship" and "landed"
+
+    When I run "kubectl exec xwing -- curl -sm10 -XPOST deathstar.default.svc.cluster.local/v1/request-landing"
+    And wait "5 seconds"
+    Then the output contains "ship" and "landed"
+
+    Scenario: Test number2 if policies work properly
+    When I run "kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.6/examples/minikube/sw_l3_l4_policy.yaml"
+    And I run "kubectl exec tiefighter -- curl -sm10 -XPOST deathstar.default.svc.cluster.local/v1/request-landing"
+    Then the output contains "ship" and "landed"
+
+    When I run "kubectl exec xwing -- curl -sm10 -XPOST deathstar.default.svc.cluster.local/v1/request-landing" expecting ERROR
+    And wait "10 seconds"
+    Then the error contains "exit" and "28"
+
+    Scenario: Inspecting the policies
+    When I run "kubectl -n kube-system get pods -l k8s-app=cilium"
+    Then the output contains "cilium-" and "running"
+    When VARIABLE "cilium-container" equals ContainerFROMOutput "cilium"
+    And VARIABLE "command5" equals "kubectl -n kube-system exec " plus VAR:"cilium-container" plus " -- cilium endpoint list"
+    And I run VAR:"command5"
+    And grep for "class=deathstar"
+    Then the output contains "enabled" and "disabled"
+    And I run VAR:"command5"
+    And grep for "class=xwing"
+    Then the output contains "disabled" and "disabled"
+    And I run VAR:"command5"
+    And grep for "class=tiefighter"
+    Then the output contains "disabled" and "disabled"
+    And I run "kubectl get cnp"
+    When VARIABLE "cilium-rule" equals ContainerFROMOutput "rule"
+    And VARIABLE "command6" equals "kubectl describe cnp " plus VAR:"cilium-rule"
+    And grep for "Class:" 
+    Then the output contains "deathstar" and "deathstar"
+    And grep for "Org:"
+    Then the output contains "empire" and "empire"
+    And grep for "Description:"
+    Then the output contains "policy to restrict" and "empire ships only"
+
+    Scenario: Applying new policy for exhaust port
+    When I run "kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1.6/examples/minikube/sw_l3_l4_l7_policy.yaml"
+    Then the output contains "ciliumnetworkpolicy" and "configured"
+    And wait "1 seconds"
+    #When I run "kubectl exec tiefighter -- curl -s -XPOST deathstar.default.svc.cluster.local/v1/request-landing"
+    #Then the output contains "Ship" and "landed"
+    #When I run "kubectl exec tiefighter -- curl -s -XPOST deathstar.default.svc.cluster.local/v1/exhaust-port"
+    #Then the output contains "Access" and "denied"
+
+
+    Scenario: Deleting the policies
+    When I run "kubectl delete -f https://raw.githubusercontent.com/cilium/cilium/v1.6/examples/minikube/sw_l3_l4_l7_policy.yaml"
+    Then the output contains "ciliumnetworkpolicy" and "deleted"
+
+    Scenario: Deleting the pods
+    When VARIABLE "work-folder" I get from CONFIG
+    When I run "kubectl delete -f https://raw.githubusercontent.com/cilium/cilium/v1.6/examples/minikube/http-sw-app.yaml"
+    Then the output contains "deathstar" and "deleted"
+    Then the output contains "xwing" and "deleted"
+    Then the output contains "tiefighter" and "deleted"

features/cilium/cilium-bsc#1121353.feature

@@ -0,0 +1,28 @@
+#TC description: https://github.com/SUSE/caasp-test-cases/pull/22/files#diff-6b705e1a52bb5b33c1c2efee4a329c2f
+#BUG: https://bugzilla.suse.com/show_bug.cgi?id=1121353
+#PR: https://github.com/SUSE/skuba/pull/967
+
+Feature: bsc#1121353 - Kubernetes – Master node pod configured with Privileged PSP
+
+Scenario: Checking if Privileged Pods
+    Given "skuba" exist in gopath
+    And VARIABLE "work-folder" I get from CONFIG
+    When I run "skuba cluster status" in VAR:"work-folder" directory
+    Then the output contains "master" and "worker"
+    When I run "kubectl get all --namespace=kube-system"
+    Then the output contains "cilium" and "dex"
+
+    When I run "kubectl get pods --namespace=kube-system"
+    When VARIABLE "privileged-pods" equals ContainersFROMOutput "cilium-"
+    And VARIABLES "commandchecks" equals "kubectl describe pod -n kube-system " plus VAR:"privileged-pods"
+    And I run VARS:"commandchecks" and check for "psp" and "kubernetes.io/psp: suse.caasp.psp.privileged"
+
+    When I run "kubectl get pods --namespace=kube-system"
+    When VARIABLE "privileged-pods" equals ContainersFROMOutput "kube-proxy-"
+    And VARIABLES "commandchecks" equals "kubectl describe pod -n kube-system " plus VAR:"privileged-pods"
+    And I run VARS:"commandchecks" and check for "psp" and "kubernetes.io/psp: suse.caasp.psp.privileged"
+
+    When I run "kubectl get pods --namespace=kube-system"
+    When VARIABLE "privileged-pods" equals ContainersFROMOutput "kured-"
+    And VARIABLES "commandchecks" equals "kubectl describe pod -n kube-system " plus VAR:"privileged-pods"
+    And I run VARS:"commandchecks" and check for "psp" and "kubernetes.io/psp: suse.caasp.psp.privileged"

features/cluster/status.feature

@@ -3,8 +3,8 @@
 Feature: Skuba cluster status
 
   Scenario: checkout cluster status
-    Given there is "cluster" directory
+    Given VARIABLE "cluster" I get from CONFIG
     And "skuba" exist in gopath
-    When I run "skuba cluster status" in "cluster" directory
+    When I run "skuba cluster status" in VAR:"cluster" directory
     Then the output contains "master"
     And the output contains "worker"

features/kured/kured-01.feature

@@ -0,0 +1,26 @@
+# TC:   https://github.com/fgerling/bdd-poc
+# This is a basic test for kured (no PR or BSC provided)
+
+Feature: Check if reboot triggered
+
+Scenario: Checking if reboot triggered on one node
+    Given "skuba" exist in gopath
+    And VARIABLE "imba-cluster" I get from CONFIG
+    When I run "skuba cluster status" in VAR:"imba-cluster" directory
+    Then the output contains "master" and "worker"
+    When I run "kubectl get all --namespace=kube-system"
+    Then the output contains "cilium" and "dex"
+
+    When I run "kubectl get daemonset kured -o yaml -n kube-system"
+    And I insert in OUTPUT "- --period=30s" and save it to kurednew.yaml
+    And I run "kubectl apply -f kurednew.yaml"
+    Then the output contains "configured"
+    And wait "30 seconds"
+    When I run "kubectl get pods --namespace=kube-system"
+    When VARIABLE "privileged-pods" equals ContainersFROMOutput "kured-"
+    And VARIABLES "commandchecks" equals "kubectl describe pod -n kube-system " plus VAR:"privileged-pods"
+    And I run VARS:"commandchecks" and IPSFromOutput
+    And I run SSHCMD "sudo touch /var/run/reboot-required" on MASTER
+    And wait "140 seconds"
+    And I run SSHCMD "sudo crictl ps" on MASTER
+    Then the output contains "seconds" or "a minute"

features/skuba_upgrade/skuba_upgrade-01.feature

@@ -0,0 +1,93 @@
+# TC:   https://github.com/SUSE/caasp-test-cases
+# PR:   https://github.com/SUSE/skuba/pull/911
+# FEATURE: skuba cluster upgrade
+
+# You are expected to run this test on a cluster bootstrapped with kubernetes-1.15.2
+Feature: Check if cluster upgrade is fine
+
+Scenario: Checking if cluster exists
+    Given "skuba" exist in gopath
+    And VARIABLE "imba-cluster" I get from CONFIG
+    When I run "skuba cluster status" in VAR:"imba-cluster" directory
+    Then the output contains "master" and "worker"
+    Then the output contains "1.15.2"
+    When I run "kubectl get all --namespace=kube-system"
+    Then the output contains "cilium" and "dex"
+    When I run "skuba version"
+    Then the output contains "v1.0.2" or "v1.1.2"
+
+    When I run "skuba cluster upgrade plan" in VAR:"imba-cluster" directory
+    Then the output contains "current kubernetes" and "latest kubernetes"
+    #Then the output contains "upgrade path to update"
+    #Then the output contains "addon upgrades from"
+
+<<<<<<< HEAD
+    When I run "skuba addon upgrade apply" expecting ERROR:"unknown addon" in VAR:"imba-cluster" directory
+    Then the error contains "metrics" and " "
+    Then the output contains "congratulations" or "not all" or "successfully"
+=======
+    When I run "zypper -n in skuba-1.2.1"
+    Then the output contains "installed"
+
+    When I run "skuba cluster upgrade plan" in VAR:"imba-cluster" directory
+    Then the output contains "current kubernetes" and "latest kubernetes"
+    #Then the output contains "upgrade path to update"
+    #Then the output contains "addon upgrades from"
+
+    When I run "skuba addon upgrade apply" in VAR:"imba-cluster" directory
+    Then the output contains "congratulations" or "ot all"
+>>>>>>> 0ea92486ed0ea35bac64f5ebea1989dd4b9f4019
+
+Scenario: Applying upgrade on nodes
+    When I run "kubectl get pods --namespace=kube-system"
+    And VARIABLE "imba-cluster" I get from CONFIG
+    When VARIABLE "privileged-pods" equals ContainersFROMOutput "kured-"
+    And VARIABLES "commandchecks" equals "kubectl describe pod -n kube-system " plus VAR:"privileged-pods"
+    And I run VARS:"commandchecks" and IPSFromOutput
+
+    #UPGRADING MASTERS FIRST
+    When VARIABLES "commandupgrades" equals "skuba node upgrade plan " plus Master Nodes
+    And I run UPGRADE VARS:"commandupgrades" in VAR:"imba-cluster" directory
+    Then the output contains "apiserver" and "controller-manager" and "scheduler"
+    And the output contains "etcd" and "kubelet" and "cri-o"
+    And I run UPGRADE VARS:"commandupgrades" in VAR:"imba-cluster" directory
+    Then the output contains "apiserver" and "controller-manager" and "scheduler"
+    And the output contains "etcd" and "kubelet" and "cri-o"
+    And I run UPGRADE VARS:"commandupgrades" in VAR:"imba-cluster" directory
+    Then the output contains "apiserver" and "controller-manager" and "scheduler"
+    And the output contains "etcd" and "kubelet" and "cri-o"
+
+    When VARIABLES "upgradeapply" equals "skuba node upgrade apply --user sles --sudo --target " plus Master Node IPS
+    And I run UPGRADE VARS:"upgradeapply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+    And wait "120 seconds"
+    And I run UPGRADE VARS:"upgradeapply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+    And wait "120 seconds"
+    And I run UPGRADE VARS:"upgradeapply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+    And wait "120 seconds"
+
+
+# UPGRADING THEN WORKERS 
+    #Scenario: Upgrading Workers
+    When VARIABLES "commandupgrades2" equals "skuba node upgrade plan " plus Worker Nodes
+    And VARIABLE "imba-cluster" I get from CONFIG
+    And I run UPGRADE VARS:"commandupgrades2" in VAR:"imba-cluster" directory
+    Then the output contains "kubelet" and "cri-o"
+    And I run UPGRADE VARS:"commandupgrades2" in VAR:"imba-cluster" directory
+    Then the output contains "kubelet" and "cri-o"
+
+    When VARIABLES "upgradeapply2" equals "skuba node upgrade apply --user sles --sudo --target " plus Worker Node IPS
+    And I run UPGRADE VARS:"upgradeapply2" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+
+    When I run "skuba addon upgrade apply" expecting ERROR:"unknown addon" in VAR:"imba-cluster" directory
+    Then the output contains "not all nodes" or "successfully" or "congratulations"
+
+    When VARIABLES "upgradeapply3" equals "skuba node upgrade apply --user sles --sudo --target " plus Worker Node IPS
+    And I run UPGRADE VARS:"upgradeapply3" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+
+    When I run "skuba addon upgrade apply" expecting ERROR:"unknown addon" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "congratulations" or "not all nodes"

features/skuba_upgrade/skuba_upgrade-02.feature

@@ -0,0 +1,86 @@
+# TC:   https://github.com/SUSE/caasp-test-cases
+# PR:   https://github.com/SUSE/skuba/pull/911
+# FEATURE: skuba cluster upgrade
+
+# You are expected to run this test on a cluster bootstrapped with kubernetes-1.16.2
+Feature: Check if cluster upgrade is fine
+
+Scenario: Checking if cluster exists
+    Given "skuba" exist in gopath
+    And VARIABLE "imba-cluster" I get from CONFIG
+    When I run "skuba cluster status" in VAR:"imba-cluster" directory
+    Then the output contains "master" and "worker"
+    Then the output contains "1.16.2"
+    When I run "kubectl get all --namespace=kube-system"
+    Then the output contains "cilium" and "dex"
+    When I run "skuba version"
+    Then the output contains "v1.2.4" or "v1.3.1" or "1.2.9"
+
+    When I run "skuba cluster upgrade plan" in VAR:"imba-cluster" directory
+    Then the output contains "current kubernetes" and "latest kubernetes"
+    #Then the output contains "upgrade path to update"
+    #Then the output contains "addon upgrades from"
+
+    When I run "zypper -n in skuba-1.3.1"
+    Then the output contains "installed"
+
+    When I run "skuba cluster upgrade plan" in VAR:"imba-cluster" directory
+    Then the output contains "current kubernetes" and "latest kubernetes"
+    #Then the output contains "upgrade path to update"
+    #Then the output contains "addon upgrades from"
+
+    When I run "skuba addon upgrade apply" in VAR:"imba-cluster" directory
+    Then the output contains "congratulations" or "ot all"
+
+Scenario: Applying upgrade on nodes
+    When I run "kubectl get pods --namespace=kube-system"
+    And VARIABLE "imba-cluster" I get from CONFIG
+    When VARIABLE "privileged-pods" equals ContainersFROMOutput "kured-"
+    And VARIABLES "commandchecks" equals "kubectl describe pod -n kube-system " plus VAR:"privileged-pods"
+    And I run VARS:"commandchecks" and IPSFromOutput
+
+    #UPGRADING MASTERS FIRST
+    When VARIABLES "commandupgrades" equals "skuba node upgrade plan " plus Master Nodes
+    And I run UPGRADE VARS:"commandupgrades" in VAR:"imba-cluster" directory
+    Then the output contains "apiserver" and "controller-manager" and "scheduler"
+    And the output contains "etcd" and "kubelet" and "cri-o"
+    And I run UPGRADE VARS:"commandupgrades" in VAR:"imba-cluster" directory
+    Then the output contains "apiserver" and "controller-manager" and "scheduler"
+    And the output contains "etcd" and "kubelet" and "cri-o"
+    And I run UPGRADE VARS:"commandupgrades" in VAR:"imba-cluster" directory
+    Then the output contains "apiserver" and "controller-manager" and "scheduler"
+    And the output contains "etcd" and "kubelet" and "cri-o"
+
+    When VARIABLES "upgradeapply" equals "skuba node upgrade apply --user sles --sudo --target " plus Master Node IPS
+    And I run UPGRADE VARS:"upgradeapply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+    And wait "120 seconds"
+    And I run UPGRADE VARS:"upgradeapply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+    And wait "120 seconds"
+    And I run UPGRADE VARS:"upgradeapply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+    And wait "120 seconds"
+
+# UPGRADING THEN WORKERS 
+    #Scenario: Upgrading Workers
+    When VARIABLES "commandupgrades2" equals "skuba node upgrade plan " plus Worker Nodes
+    And VARIABLE "imba-cluster" I get from CONFIG
+    And I run UPGRADE VARS:"commandupgrades2" in VAR:"imba-cluster" directory
+    Then the output contains "kubelet" and "cri-o"
+    And I run UPGRADE VARS:"commandupgrades2" in VAR:"imba-cluster" directory
+    Then the output contains "kubelet" and "cri-o"
+
+    When VARIABLES "upgradeapply2" equals "skuba node upgrade apply --user sles --sudo --target " plus Worker Node IPS
+    And I run UPGRADE VARS:"upgradeapply2" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+
+    When I run "skuba addon upgrade apply" in VAR:"imba-cluster" directory
+    Then the output contains "not all nodes" or "successfully" or "congratulations"
+
+    When VARIABLES "upgradeapply3" equals "skuba node upgrade apply --user sles --sudo --target " plus Worker Node IPS
+    And I run UPGRADE VARS:"upgradeapply3" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "to date" or "there are addon upgrades available"
+
+    When I run "skuba addon upgrade apply" in VAR:"imba-cluster" directory
+    Then the output contains "successfully" or "congratulations"

features/skuba_upgrade/skuba_upgrade-bsc#1167320.feature

@@ -0,0 +1,31 @@
+# TC:   https://github.com/SUSE/caasp-test/features/skuba_upgrade/skuba_upgrade_bsc#1167320.feature
+# PR:   https://github.com/SUSE/skuba/pull/1018
+# BSC:  https://bugzilla.suse.com/show_bug.cgi?id=1167320
+# FEATURE: skuba addon upgrade
+
+# You are expected to run this test on a cluster bootstrapped with kubernetes-1.15.2
+Feature: Check if cluster upgrade is fine
+
+Scenario: Checking if cluster exists
+    Given "skuba" exist in gopath
+    And VARIABLE "imba-cluster" I get from CONFIG
+    When I run "skuba cluster status" in VAR:"imba-cluster" directory
+    Then the output contains "master" and "worker"
+    Then the output contains "1.15.2"
+    When I run "kubectl get all --namespace=kube-system"
+    Then the output contains "cilium" and "dex"
+    When I run "skuba version"
+    Then the output contains "v1.2.6" or "v1.2.7"
+
+    When I run "skuba addon upgrade plan" in VAR:"imba-cluster" directory
+    Then the output contains "congratulations" or "are already"
+
+    When I run "kubectl get configmaps skuba-config -n kube-system -o yaml" in VAR:"imba-cluster" directory
+    And I replace Cilium Version in OUTPUT and save it into skubaconf.yaml file
+
+    When I run "cat skubaconf.yaml"
+    And I replace Gangway Version in OUTPUT and save it into skubaconf.yaml file
+    And I run "kubectl apply -f skubaconf.yaml"
+    And I run "skuba addon upgrade plan" in VAR:"imba-cluster" directory
+    Then the output contains "cilium" and "gangway"
+    Then the output contains "->" and "1.5.1" and "2.1.0-rev4"

features/status.feature

@@ -0,0 +1,10 @@
+# doc: https://github.com/SUSE/skuba/blob/master/README.md
+
+Feature: Skuba cluster status
+
+  Scenario: checkout cluster status
+    Given there is "imba-cluster" directory
+    And "skuba" exist in gopath
+    When I run "skuba cluster status" in "imba-cluster" directory
+    Then the output contains "master"
+    And the output contains "worker"