Update Web3signer + Lighthouse

charts/lighthouse-validator/Chart.yaml

@@ -16,13 +16,13 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 5.1.3
+version: 5.2.0
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "5.1.3"
+appVersion: "5.2.0"
 
 dependencies:
   - name: common

charts/lighthouse-validator/values.yaml

@@ -32,7 +32,7 @@ global:
   serviceAccount:
     # Specifies whether a service account should be created
     create: true
-  
+
   ## Monitoring
   ## Additional settings could be made in non-global section.
   ##
@@ -57,7 +57,7 @@ global:
       ## Create a custom prometheusRule Resource for scraping metrics using PrometheusOperator
       ##
       enabled: false
-  
+
   ## Configure liveness and readiness probes
   ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
   ## NB! readinessProbe and livenessProbe must be disabled before fully synced
@@ -97,7 +97,7 @@ image:
   repository: sigp/lighthouse
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "v5.1.3"
+  tag: "v5.2.0"
 
 imagePullSecrets: []
 nameOverride: ""
@@ -119,7 +119,8 @@ securityContext:
 service:
   type: ClusterIP
 
-resources: {}
+resources:
+  {}
   # We usually recommend not to specify default resources and to leave this as a conscious
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following

charts/lighthouse/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: lighthouse
-version: 5.1.3
+version: 5.2.0
 kubeVersion: "^1.20.0-0"
 description: Rust Ethereum 2.0 Client.
 type: application
@@ -16,7 +16,7 @@ sources:
 maintainers:
   - name: Dmitri Tsumak
     email: [email protected]
-appVersion: v5.1.3
+appVersion: v5.2.0
 
 dependencies:
   - name: common

charts/lighthouse/values.yaml

@@ -35,7 +35,7 @@ global:
   serviceAccount:
     # Specifies whether a service account should be created
     create: true
-  
+
   ## RBAC configuration.
   ## ref: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
   ## Additional settings could be made in non-global section.
@@ -44,7 +44,7 @@ global:
     ## Specifies whether RBAC resources are to be created
     ##
     create: true
-  
+
   ## Monitoring
   ## Additional settings could be made in non-global section.
   ##
@@ -69,7 +69,7 @@ global:
       ## Create a custom prometheusRule Resource for scraping metrics using PrometheusOperator
       ##
       enabled: false
-  
+
   ## Configure liveness and readiness probes
   ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
   ## NB! readinessProbe and livenessProbe must be disabled before fully synced
@@ -108,7 +108,7 @@ sidecar:
 image:
   registry: "docker.io"
   repository: "sigp/lighthouse"
-  tag: "v5.1.3"
+  tag: "v5.2.0"
   pullPolicy: IfNotPresent
 
 ## Credentials to fetch images from private registry
@@ -141,7 +141,7 @@ http:
 ## If set, lighthouse will perform a checkpoint sync. For more information see here: https://lighthouse-book.sigmaprime.io/checkpoint-sync.html
 ## Respective public checkpoint sync endpoints can be found here: https://eth-clients.github.io/checkpoint-sync-endpoints/
 ## It is not recommended to blindly trust any public beacon node.
-## Therefore please verify that you are on the correct chain: https://notes.ethereum.org/@launchpad/checkpoint-sync#1-Obtaining-finalized-checkpoint-amp-state-root 
+## Therefore please verify that you are on the correct chain: https://notes.ethereum.org/@launchpad/checkpoint-sync#1-Obtaining-finalized-checkpoint-amp-state-root
 ##
 checkpointSyncUrl: ""
 
@@ -192,23 +192,23 @@ rbac:
     ##
     - apiGroups: [""]
       resources:
-      - "nodes"
+        - "nodes"
       verbs:
-      - "get"
-      - "list"
-      - "watch"
+        - "get"
+        - "list"
+        - "watch"
   ## Required Role rules
   ##
   rules:
     ## Required to get information about the serices nodePort.
     ##
     - apiGroups: [""]
       resources:
-      - "services"
+        - "services"
       verbs:
-      - "get"
-      - "list"
-      - "watch"
+        - "get"
+        - "list"
+        - "watch"
 
 ## Node labels for pod assignment
 ## ref: https://kubernetes.io/docs/user-guide/node-selection/

charts/validators/Chart.yaml

@@ -16,13 +16,13 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 3.7.1
+version: 3.7.2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "v3.7.1"
+appVersion: "v3.7.2"
 
 keywords:
   - ethereum

charts/validators/values.yaml

@@ -115,7 +115,7 @@ image:
   lighthouse:
     registry: "docker.io"
     repository: "sigp/lighthouse"
-    tag: "v5.1.3"
+    tag: "v5.2.0"
   teku:
     registry: "docker.io"
     repository: "consensys/teku"

charts/web3signer-validators/Chart.yaml

@@ -16,13 +16,13 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 6.1.1
+version: 6.1.2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "v6.1.1"
+appVersion: "v6.1.2"
 
 keywords:
   - ethereum

charts/web3signer-validators/values.yaml

@@ -117,7 +117,7 @@ image:
   lighthouse:
     registry: "docker.io"
     repository: "sigp/lighthouse"
-    tag: "v5.1.3"
+    tag: "v5.2.0"
   teku:
     registry: "docker.io"
     repository: "consensys/teku"

charts/web3signer/Chart.yaml

@@ -16,13 +16,13 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 6.0.3
+version: 6.0.4
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "v24.2.0"
+appVersion: "v24.6.0"
 
 keywords:
   - ethereum

charts/web3signer/values.yaml

@@ -20,7 +20,7 @@ image:
   repository: consensys/web3signer
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "24.2.0"
+  tag: "24.6.0"
 
 ## Init image is used to chown data volume, etc.
 ##