111 create a configure cluster command

[Marios85]

This PR closes #111. Tweaked the existing code for setting up a namespace so the job-deployment accounts have permission to create namespaces. This in turn is called by the new command to configure the cluster.

[AlexIoannides]

A couple of points - happy to jump on a call to discuss.

[AlexIoannides]

I think the logic is good-to-go - we just need to get the naming sorted so that it makes sense.

We have two sets of entity that required service-accounts:

• pods running the workflow-controller (i.e. in a 'deployment job'); and,
• pods that form the stages of a workflow (be them jobs or k8s-deployment resources).

Prior to this PR, we have BODYWORK_WORKFLOW_SERVICE_ACCOUNT for the first entity and BODYWORK_JOBS_DEPLOYMENTS_SERVICE_ACCOUNT for the second.

We need to pick names that done't confuse in the future.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (v3.0.0@2f2a0b7). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             v3.0.0     #113   +/-   ##
=========================================
  Coverage          ?   97.90%           
=========================================
  Files             ?       21           
  Lines             ?     1383           
  Branches          ?        0           
=========================================
  Hits              ?     1354           
  Misses            ?       29           
  Partials          ?        0           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2f2a0b7...20a1c0a. Read the comment docs.

[Marios85]

Renaming has been done and added a test fixture that configures the cluster for the tests that require it.

[AlexIoannides]

setup_workflow_service_account(...) needs a little modification, so that the workflow-controller is authorised to delete namespaces, as well.

[AlexIoannides]

Just a couple of minor point and then good to go - doesn't need another review.

[Marios85]

I have made the changes.

I didn't add the delete command as I thought that the user would be issuing the command to delete a namespace but then I suppose the workflow controller might want to tear down the namespace on fail etc.

[AlexIoannides]

Yes, that's right - if a deployment doesn't leave any services hanging around (i.e. just batch jobs), we should probably delete the namespace, too.