Allow to specify a cluster name in test suite

[johscheuer]

Description

Depending on the test case it would be useful to reuse a cluster, e.g. in cases where a test cluster gets loaded with some amount of data.

Type of change

Please select one of the options below.

• New feature (non-breaking change which adds functionality)

Discussion

Are there any design details that you would like to discuss further?

Testing

Ran a manual test:

NAMESPACE=jdev CLUSTER_NAME=jdev  make -C e2e test_operator.run

With the following cluster and Pods created (the cluster is not available as the data loader is active):

$ kubectl -n jdev get fdb,po 
NAME                                             GENERATION   RECONCILED   AVAILABLE   FULLREPLICATION   VERSION   AGE
foundationdbcluster.apps.foundationdb.org/jdev   1                                                       7.1.53    4m46s

NAME                                                              READY   STATUS    RESTARTS   AGE
pod/jdev-log-1                                                    2/2     Running   0          4m45s
pod/jdev-log-2                                                    2/2     Running   0          4m45s
pod/jdev-log-3                                                    2/2     Running   0          4m45s
pod/jdev-log-4                                                    2/2     Running   0          4m45s
pod/jdev-log-5                                                    2/2     Running   0          4m45s
pod/jdev-stateless-1                                              2/2     Running   0          4m45s
pod/jdev-stateless-2                                              2/2     Running   0          4m45s
pod/jdev-stateless-3                                              2/2     Running   0          4m45s
pod/jdev-stateless-4                                              2/2     Running   0          4m45s
pod/jdev-stateless-5                                              2/2     Running   0          4m45s
pod/jdev-stateless-6                                              2/2     Running   0          4m45s
pod/jdev-stateless-7                                              2/2     Running   0          4m45s
...

Documentation

Added

Follow-up

[foundationdb-ci]

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

• Commit ID: 874082f
• Duration 1:43:55
• 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)

[nicmorales9]

Looks reasonable to me, if it works in your tests then ship it 😄