Offline mode using ConfigMap instead of Volume

[karoisuzvards]

Is your feature request related to a problem? Please describe.

We are (a paying customer) using Launchdarkly Relay in Offline Mode for dynamic environments. Initial state is seeded by downloading the tarball using relay key (as per docs). Due to cost saving we are using AWS Spot instances which can terminate at any moment. When PVC is created and seeded with file - if/when SPOT termination occurs - newly created PVC is empty which could cause trouble for our ephemeral environment.

Describe the solution you'd like

In our case - the seed file is small - 6Kib. We could push it inside a ConfigMap and mount it as a volume (https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#populate-a-volume-with-data-stored-in-a-configmap)

Describe alternatives you've considered

Looking at deployment.yaml - we might hack something up by creating a ConfigMap ending in -volume and using relay.volume.offline flag (to be tested first though)

[keelerm84]

@karoisuzvards this is already supported.

As you mention, simply load the offline.tar.gz into a config map.

kubectl create configmap offline-configmap --from-file=offline.tar.gz

Then reference that file, and configmap definition in the volumes section of your values file.

relay:
  volume:
    offline: offline.tar.gz
    definition:
      configMap:
        name: offline-configmap