traffic: give the sender the chain list it mounts

The volume named traffic-chains-gc7kb89hm9, a hash-suffixed ConfigMap no
generator in this repo produces, so it never existed and the pod has sat in
ContainerCreating -- MountVolume.SetUp failed, configmap not found -- for as
long as the Deployment has. A chain with no sender does not build blocks, which
is why mainnet has been flat.

The list names lux-chain, the address that answers eth_chainId 0x17871 and a
rising height. luxd-rpc fronts the StatefulSet whose bootstrap peers no longer
accept a connection, so every path under it is 404.

Co-authored-by: Hanzo Dev <[email protected]>

deploy/lux-mainnet/traffic.yaml

@@ -49,5 +49,22 @@ volumeMounts:
 volumes:
 - configMap:
     defaultMode: 420
-    name: traffic-chains-gc7kb89hm9
+    name: traffic-chains
   name: chains
+
+# The chain list this bot sends to. It has to live here, in the values the chart
+# renders: the volume named `traffic-chains-gc7kb89hm9`, a hash-suffixed name no
+# generator in this repo produces, so the ConfigMap never existed and the pod sat
+# in ContainerCreating -- `MountVolume.SetUp failed: configmap not found` -- for
+# as long as the Deployment has. A chain with no sender does not build blocks.
+#
+# lux-chain is the address that answers: eth_chainId 0x17871 and a rising height.
+# luxd-rpc fronts the in-cluster StatefulSet, whose bootstrap peers no longer
+# accept a connection, so it 404s every path under /v1/chain/c/rpc.
+configMaps:
+- name: traffic-chains
+  data:
+    chains.json: |
+      [
+        {"name":"lux-cchain","rpc":"http://lux-chain.lux-mainnet.svc.cluster.local/v1/chain/c/rpc","key":"$TRAFFIC_KEY","weight":1,"dex":0}
+      ]