Support binding PVC to specific PV

[planetf1]

Scenario

• Volumes are not automatically defined
• PVC requests will not complete

• Egeria will not start

  Required

  • Define volume manually
  • specific identifier for storage volume (PV) in our claims - for kafka, zookeeper, egeria, jupyter etc etc
  • Egeria will start

Currently egeria charts are only tested in environments where storage is automatically allocated. There are some issues open to support 'StorageClass' consistently. (currently we use the default storageclass)

The ‘claim’ is the request for storage usually ‘the system’ will look at various aspects of the claim and decide which volume to allocate

For manual assignment, one suggestion is here -> https://stackoverflow.com/questions/34282704/can-a-pvc-be-bound-to-a-specific-pv

It looks like you would need to define the pv name in the spec of the pvc. That should probably be a variable exposed to the values file, and default to not being specified

For egeria pods, and for jupyter (since we define the pod) that seems fairly easy.

For kafka/zookeeper it would need to be in our kafka_cluster definition. https://strimzi.io/docs/operators/in-development/configuring.html has appropriate information

@dwolfson Can you add any further clarification on the scenario, how volumes are allocated, and what identifiers need to be matched

As a workaround it may be possible to retrospectively EDIT the PVCs that egeria has created, and modify appropriate fields to allow the pvc-pv link to be made

[planetf1]

On further investigation it appears that the ability to specify storage class is in fact sufficient. This was added in #252