chore: update kms-connector config

Author: piizama

mainnet/helm-values/kms-connector.yaml

@@ -5,15 +5,10 @@ commonConfig:
   gatewayUrl: "$(CONDUIT_RPC_HTTP_URL)"
   chainId: "261131"
   gatewayContractAddresses:
-    decryption: "TODO_MAINNET"
-    gatewayConfig: "TODO_MAINNET"
-    kmsGeneration: "TODO_MAINNET"
+    decryption: "0x0f6024a97684f7d90ddb0fAAD79cB15F2C888D24"
+    gatewayConfig: "0xDE537Be194777A56f8B19d14079E6a78249390ab"
+    kmsGeneration: "0x290947F9fed2d91fdB22f35E162aDfA744b7aEe3"
   env:
-    - name: CONDUIT_RPC_HTTP_URL
-      valueFrom:
-        secretKeyRef:
-          name: conduit
-          key: conduit-rpc-http-url
     - name: DATABASE_ENDPOINT
       valueFrom:
         secretKeyRef:
@@ -29,12 +24,17 @@ commonConfig:
         secretKeyRef:
           name: connector-database
           key: password
+    - name: CONDUIT_RPC_HTTP_URL
+      valueFrom:
+        secretKeyRef:
+          name: conduit
+          key: conduit-rpc-http-url
 
 kmsConnectorDbMigration:
   enabled: true
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/db-migration
-    tag: v0.9.13
+    tag: v0.10.7
   env: []
   affinity:
     nodeAffinity:
@@ -56,9 +56,11 @@ kmsConnectorGwListener:
   nameOverride: kms-connector-gw-listener
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/gw-listener
-    tag: v0.9.13
-  # Set 2 replicas for more resiliency and proper rolling upgrades
-  replicas: 2
+    tag: v0.10.7
+  replicas: 1
+  config:
+    # Use full node
+    gatewayUrl: "http://gateway-node:8547"
   affinity:
     nodeAffinity:
       requiredDuringSchedulingIgnoredDuringExecution:
@@ -79,7 +81,7 @@ kmsConnectorKmsWorker:
   nameOverride: kms-connector-kms-worker
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/kms-worker
-    tag: v0.9.13
+    tag: v0.10.7
   replicas: 1
   config:
     kmsCoreEndpoints: "http://kms-core:50100"
@@ -103,7 +105,7 @@ kmsConnectorTxSender:
   nameOverride: kms-connector-tx-sender
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/tx-sender
-    tag: v0.9.13
+    tag: v0.10.7
   replicas: 1
   serviceAccountName: mpc-party-connector
   wallet:

testnet/helm-values/kms-connector.yaml

@@ -34,7 +34,7 @@ kmsConnectorDbMigration:
   enabled: true
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/db-migration
-    tag: v0.10.0
+    tag: v0.10.7
   env: []
   affinity:
     nodeAffinity:
@@ -56,8 +56,8 @@ kmsConnectorGwListener:
   nameOverride: kms-connector-gw-listener
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/gw-listener
-    tag: v0.10.0
-  replicas: 2
+    tag: v0.10.7
+  replicas: 1
   config:
     # Use full node
     gatewayUrl: "http://gateway-node:8547"
@@ -81,7 +81,7 @@ kmsConnectorKmsWorker:
   nameOverride: kms-connector-kms-worker
   image:
     name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/kms-worker
-    tag: v0.10.0
+    tag: v0.10.7
   replicas: 1
   config:
     kmsCoreEndpoints: "http://kms-core:50100"
@@ -104,19 +104,17 @@ kmsConnectorTxSender:
   enabled: true
   nameOverride: kms-connector-tx-sender
   image:
-    name: hub.zama.ai/zama-protocol/zama-ai/fhevm/kms-connector/tx-sender
-    tag: v0.9.3
+    name: hub.zama.org/zama-protocol/zama-ai/fhevm/kms-connector/tx-sender
+    tag: v0.10.7
   replicas: 1
+  serviceAccountName: mpc-party-connector
   wallet:
+    # Use the kms-connector tx-sender KMS key as ethereum wallet
     awsKms:
       enabled: true
       configmap:
         name: mpc-party
         key: KMS_CONNECTOR__TX_SENDER_AWS_KMS_KEY_ID
-    # The secret can be removed after migrating to AWS KMS
-    #secret:
-    #  name: connector-wallet-keys
-    #  key: kms_txsender_1.private_key
   affinity:
     nodeAffinity:
       requiredDuringSchedulingIgnoredDuringExecution: