From a9cde7ac70aaedd9a8ca7cce41c4d12529347893 Mon Sep 17 00:00:00 2001 From: Sebastian Cole Date: Wed, 29 Sep 2021 12:28:46 +1000 Subject: [PATCH] Adding BDD tests for locked instance groups --- test-bdd/features/01_create.feature | 9 +++++++++ test-bdd/features/03_upgrade.feature | 6 ++++++ test-bdd/features/04_delete.feature | 6 ++++++ 3 files changed, 21 insertions(+) diff --git a/test-bdd/features/01_create.feature b/test-bdd/features/01_create.feature index 2a9f84e5..0d75c9c6 100644 --- a/test-bdd/features/01_create.feature +++ b/test-bdd/features/01_create.feature @@ -17,6 +17,7 @@ Feature: CRUD Create And I create a resource instance-group-launch-template-mixed.yaml And I create a resource manager-configmap.yaml And I create a resource instance-group-gitops.yaml + And I create a resource instance-group-locked.yaml Scenario: Create an instance-group with rollingUpdate strategy Given an EKS cluster @@ -88,3 +89,11 @@ Feature: CRUD Create And the resource should converge to selector .status.currentState=ready And the resource condition NodesReady should be true And 2 nodes should be ready + + Scenario: Create an instance-group with latest ami + Given an EKS cluster + When I create a resource instance-group-locked.yaml + Then the resource should be created + And the resource should converge to selector .status.currentState=ready + And the resource condition NodesReady should be true + And 2 nodes should be ready diff --git a/test-bdd/features/03_upgrade.feature b/test-bdd/features/03_upgrade.feature index 2209b66e..0af60df1 100644 --- a/test-bdd/features/03_upgrade.feature +++ b/test-bdd/features/03_upgrade.feature @@ -61,3 +61,9 @@ Feature: CRUD Upgrade And the resource should converge to selector .status.currentState=ready And the resource condition NodesReady should be true And 3 nodes should be ready + + Scenario: Lock an instance-group + Given an EKS cluster + When I update a resource instance-group-locked.yaml with .metadata.annotation[instancemgr.keikoproj.io/lock-upgrades] set to true + Then I update a resource instance-group-locked.yaml with .spec.eks.configuration.instanceType set to t2.medium + Then the resource should converge to selector .status.currentState=locked diff --git a/test-bdd/features/04_delete.feature b/test-bdd/features/04_delete.feature index c9b50a48..acdddaf0 100644 --- a/test-bdd/features/04_delete.feature +++ b/test-bdd/features/04_delete.feature @@ -14,6 +14,7 @@ Feature: CRUD Delete And I delete a resource instance-group-managed.yaml And I delete a resource instance-group-fargate.yaml And I delete a resource instance-group-gitops.yaml + And I delete a resource instance-group-locked.yaml Scenario: Delete an instance-group with rollingUpdate strategy Given an EKS cluster @@ -49,6 +50,11 @@ Feature: CRUD Delete Given an EKS cluster Then I delete a resource instance-group-fargate.yaml And the resource should be deleted + + Scenario: Delete a locked profile + Given an EKS cluster + Then I delete a resource instance-group-locked.yaml + And the resource should be delete Scenario: Delete an instance-group with shortened resource Given an EKS cluster