chore: remove old kuttl tests from repository (argoproj-labs#2167)

Signed-off-by: Jonathan West <jgwest@gmail.com>

Author: jgwest

.github/workflows/ci-build.yaml

@@ -50,19 +50,6 @@ jobs:
           - v1.27.1-k3s1
           - v1.33.5-k3s1
     steps:
-      - name: Download kuttl plugin
-        env:
-          KUTTL_VERSION: "0.10.0"
-          KUTTL_PLUGIN_SUM: "ad21c0d2be495a8f6cfc0821e592ae61afd191ebd453156d9b204e2524fceaf2"
-          KUTTL_PLUGIN_FILENAME: "kubectl-kuttl_0.10.0_linux_x86_64"
-        run: |
-          set -x
-          echo ${KUTTL_PLUGIN_FILENAME}
-          curl -OL https://github.com/kudobuilder/kuttl/releases/download/v${KUTTL_VERSION}/${KUTTL_PLUGIN_FILENAME}
-          echo "${KUTTL_PLUGIN_SUM}  ${KUTTL_PLUGIN_FILENAME}" | sha256sum -c -
-          sudo mv ${KUTTL_PLUGIN_FILENAME} /usr/local/bin/kubectl-kuttl
-          sudo chmod +x /usr/local/bin/kubectl-kuttl
-          kubectl-kuttl version
       - name: Install K3D
         run: |
           set -x

.gitignore

@@ -30,7 +30,6 @@ vendor/
 build/_output
 
 kubeconfig
-kuttl-test.json
 e2e.json
 
 # Desktop Services Store in macOS system

Makefile

@@ -207,14 +207,11 @@ undeploy: ## Undeploy controller from the K8s cluster specified in ~/.kube/confi
 
 ##@ E2E
 
-e2e: ## Run operator e2e tests
-	kubectl kuttl test ./tests/k8s --config ./tests/kuttl-tests.yaml
-
 
 start-e2e: install-prometheus-crds ## Start operator for E2E tests (installs required CRDs if needed)
 	ARGOCD_CLUSTER_CONFIG_NAMESPACES="argocd-e2e-cluster-config, argocd-test-impersonation-1-046, argocd-agent-principal-1-051, argocd-agent-agent-1-052, appset-argocd, appset-old-ns, appset-new-ns, appset-argocd-clusterrole, ns-hosting-principal, ns-hosting-managed-agent, ns-hosting-autonomous-agent" make run
 
-all: test install run e2e ## UnitTest, Run the operator locally and execute e2e tests.
+all: test install run ## UnitTest, Run the operator locally
 
 CONTROLLER_GEN = $(shell pwd)/bin/controller-gen
 controller-gen: ## Download controller-gen locally if necessary.

README.md

@@ -13,7 +13,7 @@ See the [documentation][docs] for installation and usage of the operator.
 
 ## E2E testing
 
-E2E tests are written using [KUTTL](https://kuttl.dev/docs/#install-kuttl-cli). Please Install [KUTTL](https://kuttl.dev/docs/#install-kuttl-cli) to run the tests.
+E2E tests are written using Ginkgo. To install Ginkgo, you can use `make ginkgo`. The expected version of Ginkgo will be downloaded into `(repository root)/bin`.
 
 Note that the e2e tests for Redis HA mode require a cluster with at least three worker nodes.  A local three-worker node
 cluster can be created using [k3d](https://k3d.io/)

docs/developer-guide/e2e-test-guide.md

@@ -1,178 +1,3 @@
 # Argo CD Operator E2E Test Guide
 
-E2E tests are written using [KUTTL](https://kuttl.dev/docs/#install-kuttl-cli).
-
-## Requirements
-
-This test suite assumes that an Argo CD Operator is installed on the cluster or running locally using `ARGOCD_CLUSTER_CONFIG_NAMESPACES=argocd-e2e-cluster-config make install run`.
-
-The system executing the tests must have following tools installed:
-
-* `kuttl` kubectl plugin (>= v0.11.1)
-* `oc` and `kubectl` client
-* `jq` for parsing JSON data
-* `curl`
-
-There should be a `kubeconfig` pointing to your cluster, user should have full admin privileges (i.e. `kubeadm`).
-
-!!! note 
-    E2E tests utilize GNU Grep under the hood. Please make sure that you have the GNU compatible `grep` installed.
-
-If you are on OSX you can install GNU compatible grep using the below command. The package is installed as `ggrep` by default. Please set this(ggrep) as an alias to `grep`.  
-
-```sh
-brew install grep
-```
-
-Use the below commands to install GNU compatible `grep` on OSX.
-
-Also, note that the e2e tests for Redis HA mode require a cluster with at least three worker nodes.  A local three-worker node
-cluster can be created using [k3d](https://k3d.io/)
-
-## Running the tests
-
-In any case, you should have set up your `kubeconfig` in such a way that your
-default context points to the cluster you want to test. You can use the
-`kubectl login ...` command to set this up for you.
-
-## Run e2e tests
-
-```sh
-make e2e
-```
-
-## Run Operator locally and execute e2e tests
-
-```sh
-make all
-```
-
-### Running manual with kuttl
-
-```sh
-kubectl kuttl test ./tests/k8s --config ./tests/kuttl-tests.yaml
-```
-
-### Running single tests
-
-Sometimes (e.g. when initially writing a test or troubleshooting an existing
-one), you may want to run single test cases isolated. To do so, you can pass
-the name of the test using `--test` to `kuttl`, i.e.
-
-```sh
-kubectl kuttl test ./tests/k8s --config ./tests/kuttl-tests.yaml --test 1-004_validate_namespace_scoped_install
-```
-
-The name of the test is the name of the directory containing its steps and
-assertions.
-
-If you are troubleshooting, you may want to prevent `kuttl` from deleting the
-test's namespace afterwards. In order to do so, just pass the additional flag
-`--skip-delete` to above command.
-
-## Writing new tests
-
-### Name of the test
-
-Each test comes in its own directory, containing all its test steps. The name
-of the test is defined by the name of this directory.
-
-The name of the test should be short, but expressive. The format for naming a
-test is currently `<test ID>_<short description>`.
-
-The `<test ID>` is the serial number of the test as defined in the Test Plan
-document. The `<short description>` is exactly that, a short description of
-what happens in the test.
-
-### Name of the test steps
-
-Each test step is a unique YAML file within the test's directory. The name of
-the step is defined by its file name.
-
-The test steps must be named `XX-<name>.yaml`. This is a `kuttl` convention
-and cannot be overriden. `XX` is a number (prefixed with `0`, so step `1` must
-be `01`), and `<name>` is a free form value for the test step.
-
-There are two reserved words you cannot use for `<name>`:
-
-* `assert` contains positive assertions (i.e. resources that must exist) and
-* `errors` contains negative assertions (i.e. resources that must not exist)
-
-Refer to the
-[kuttl documentation](https://kuttl.dev/docs)
-for more information.
-
-### Documentation
-
-Documentation is important, even for tests. You can should provide inline
-documentation in your YAML files (using comments) and a `README.md` in your
-test case's directory. The `README.md` should provide some context for the
-test case, e.g. what it tries to assert for under which circumstances. This
-will help others in troubleshooting failing tests.
-
-### Recipes
-
-`kuttl` unfortunately neither encourages or supports re-use of your test steps
-and assertions yet.
-
-Generally, you should try to use `assert` and `errors` declaration whenever
-possible and viable. For some cases, you may need to use custom scripts to
-get the results you are looking for.
-
-#### Scripts general
-
-Scripts can be executed in a `kuttl.dev/TestStep` resources from a usual test
-step declaration.
-
-Your script probably will retrieve some information, and asserts it state. If
-the assertion fails, the script should exit with a code > 0, and also print
-some information why it failed, e.g.
-
-```yaml
-apiVersion: kuttl.dev/v1beta1
-kind: TestStep
-commands:
-- script: |
-    # Get some piece of information...
-    if test "$result" != "expected"; then
-      echo "Expectation failed, should 'expected', is '$result'"
-      exit 1
-    fi
-```
-
-Also, you may want to use `set -e` and `set -o pipefail` at the top of your
-script to catch unexpected errors as test case failures, e.g.
-
-```yaml
-apiVersion: kuttl.dev/v1beta1
-kind: TestStep
-commands:
-- script: |
-    set -e
-    set -o pipefail
-    # rest of your script
-```
-
-#### Getting values of a resource's environment variables
-
-YAML declarations used in `assert` or `errors` files unfortunately don't handle
-arrays very well yet. You will always have to specify the complete expectation,
-i.e. the complete array.
-
-If you are just interested in a certain variable, and don't care about the rest,
-you can use a script similar to the following using `jq`. E.g. to get the value
-of a variable named `FOO` for the `argocd-server` deployment in the test's
-namespace:
-
-```yaml
-apiVersion: kuttl.dev/v1beta1
-kind: TestStep
-commands:
-- script: |
-    val=$(kubectl get -n $NAMESPACE deployments argocd-server -o json \
-      | jq -r '.spec.templates.spec.containers[0].env[]|select(.name=="FOO").value')
-    if test "$val" != "bar"; then
-      echo "Expectation failed for for env FOO in argocd-server: should 'bar', is '$val'"
-      exit 1
-    fi
-```
+E2E tests are written using Ginkgo. See [documentation within the source repository](https://github.com/argoproj-labs/argocd-operator/tree/master/tests/ginkgo) for additional information.