first commit

A

Author: CRThaze

.github/workflows/update-readme.yaml

@@ -0,0 +1,26 @@
+name: Generate helm docs
+run-name: Generate helm docs ${{ github.ref_name }} by @${{ github.actor }}"
+on:
+  workflow_dispatch:
+  pull_request:
+    paths:
+      - values.yaml
+      - README.md.gotmpl
+      - README.md
+      - Chart.yaml
+
+jobs:
+  update-readme:
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Render helm docs inside the README.md and push changes back to PR branch
+      uses: losisin/helm-docs-github-action@v1
+      with:
+        chart-search-root: deployment/helm_chart/opik
+        git-push: true
+        git-push-user-name: "CometActions"
+        git-push-user-email: "[email protected]"
+        git-commit-message: "Update Helm documentation"

.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

Chart.yaml

@@ -0,0 +1,24 @@
+apiVersion: v2
+name: s3proxy
+description: A Helm chart for deploying S3Proxy - Access other storage backends via the S3 API
+
+# 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.1.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: "2.7.0"