Fix the plugin e2e test setup

[johscheuer]

Description

Otherwise I saw cases where the clusters where not properly recreated.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Discussion

Testing

Ran e2e tests for the plugin manually.

Documentation

Follow-up

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 9e8588c
• Duration 2:52:26
• Result: ❌ FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[johscheuer]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 9e8588c
• Duration 2:52:26
• Result: ❌ FAILED
• Error: Error while executing command: if $fail_test; then exit 1; fi. Reason: exit status 1
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

That failure was unrelated:

Summarizing 1 Failure:
  [FAIL] Operator when the operator is allowed to reset the maintenance zone [It] should reset the maintenance mode once the Pod was restarted [e2e, pr]
  /codebuild/output/src718197840/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator/operator_test.go:2225

[foundationdb-ci]

Result of fdb-kubernetes-operator-pr on Linux CentOS 7

• Commit ID: 9e8588c
• Duration 2:56:54
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)