feat(scroll): initial commit

charts/scroll/Chart.lock

@@ -0,0 +1,6 @@
+dependencies:
+- name: common
+  repository: file://../common
+  version: 0.1.0
+digest: sha256:636a65e9846bdff17cc4e65b0849061f783759a37aa51fb85ff6fd8ba5e68467
+generated: "2024-11-24T23:41:11.186990172Z"

charts/scroll/Chart.yaml

@@ -0,0 +1,30 @@
+apiVersion: v2
+name: scroll
+description: Deploy and scale [Scroll](https://github.com/scroll-tech/go-ethereum) inside Kubernetes with ease
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+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: 0.0.1
+
+# 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.
+# renovate: image=scrolltech/l2geth
+appVersion: "scroll-v5.8.5"
+
+dependencies:
+  - name: common
+    version: 0.0.1-canary.1
+    repository: https://graphops.github.io/launchpad-charts/canary