Refactor metaflow charts with no functional changes

Author: josephsirak

.github/workflows/publish_helm_charts.yml

@@ -29,6 +29,6 @@ jobs:
     - name: Run chart-releaser
       uses: helm/[email protected]
       with:
-        charts_dir: k8s/helm/metaflow
+        charts_dir: charts/metaflow
       env:
         CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

charts/metaflow/.DS_Store

@@ -0,0 +1,28 @@
+apiVersion: v2
+appVersion: v2.4.13
+dependencies:
+  - name: metaflow-service
+    repository: ""
+    version: 0.2.0
+    condition: metaflow-service.enabled
+  - name: metaflow-ui
+    repository: ""
+    version: 0.3.0
+    condition: metaflow-ui.enabled
+  - name: postgresql
+    repository: https://charts.bitnami.com/bitnami
+    version: "^14"
+    condition: postgresql.enabled
+description: Machine Learning platform
+home: https://metaflow.org
+keywords:
+  - mlops
+  - metaflow
+  - metadata service
+  - metaflow ui
+name: metaflow
+sources:
+  - https://github.com/Netflix/metaflow
+  - https://github.com/outerbounds/metaflow-tools
+type: application
+version: 0.0.2

k8s/helm/metaflow/Chart.lock renamed to charts/metaflow/Chart.lock

@@ -0,0 +1,10 @@
+# Helm Chart for Metaflow Services
+
+This Helm chart provides a comprehensive deployment solution for Metaflow Services in a Kubernetes cluster. It includes three main components:
+
+* Metaflow Metadata Service - Manages workflow metadata and execution state
+* Metaflow UI (Frontend and Backend) - Provides web-based visualization and monitoring
+* PostgreSQL Database - Stores metadata for Metaflow services
+
+While the included PostgreSQL sub-chart enables quick evaluation and development setups, for production environments we strongly recommend using a managed PostgreSQL service (like AWS RDS). To use an external database, disable the PostgreSQL sub-chart by setting `postgresql.enabled: false`.
+

charts/metaflow/Chart.yaml

@@ -2,6 +2,9 @@
 # This supports shell glob matching, relative path matching, and
 # negation (prefixed with !). Only one pattern per line.
 .DS_Store
+Thumbs.db
+ehthumbs.db
+
 # Common VCS dirs
 .git/
 .gitignore
@@ -10,14 +13,40 @@
 .hg/
 .hgignore
 .svn/
+
 # Common backup files
 *.swp
 *.bak
 *.tmp
 *.orig
 *~
+
 # Various IDEs
 .project
 .idea/
 *.tmproj
 .vscode/
+*.suo
+*.user
+*.userossc
+*.sln.docstates
+
+# Logs
+*.log
+
+# Node.js
+node_modules/
+npm-debug.log
+yarn-error.log
+
+# Python
+__pycache__/
+*.py[cod]
+*.pyo
+*.pyd
+.Python
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/

k8s/helm/metaflow/LICENSE renamed to charts/metaflow/LICENSE

@@ -0,0 +1,19 @@
+apiVersion: v2
+appVersion: v2.4.13
+description: A Helm chart to deploy Metadata Service for Metaflow
+name: metaflow-service
+type: application
+version: 0.2.0
+maintainers:
+  - name: Savin Goyal
+    email: [email protected]
+  - name: Oleg Avdeev
+    email: [email protected]
+keywords:
+  - metaflow
+  - metadata
+  - service
+sources:
+  - https://github.com/Netflix/metaflow
+  - https://github.com/outerbounds/metaflow-tools
+icon: https://metaflow.org/images/metaflow.svg

charts/metaflow/README.md

@@ -1,22 +1,34 @@
 1. Get the application URL by running these commands:
 {{- if .Values.ingress.enabled }}
-{{- range $host := .Values.ingress.hosts }}
-  {{- range .paths }}
-  http{{ if $.Values.ingress.tls }}s{{ end }}://{{ $host.host }}{{ .path }}
+  {{- range $host := .Values.ingress.hosts }}
+    {{- range .paths }}
+      http{{ if $.Values.ingress.tls }}s{{ end }}://{{ $host.host }}{{ .path }}
+    {{- end }}
   {{- end }}
-{{- end }}
 {{- else if contains "NodePort" .Values.service.type }}
   export NODE_PORT=$(kubectl get --namespace {{ .Release.Namespace }} -o jsonpath="{.spec.ports[0].nodePort}" services {{ include "metaflow-service.fullname" . }})
   export NODE_IP=$(kubectl get nodes --namespace {{ .Release.Namespace }} -o jsonpath="{.items[0].status.addresses[0].address}")
-  echo http://$NODE_IP:$NODE_PORT
+  if [ -z "$NODE_PORT" ] || [ -z "$NODE_IP" ]; then
+    echo "Error: Unable to retrieve NodePort or Node IP."
+  else
+    echo http://$NODE_IP:$NODE_PORT
+  fi
 {{- else if contains "LoadBalancer" .Values.service.type }}
-     NOTE: It may take a few minutes for the LoadBalancer IP to be available.
-           You can watch the status of by running 'kubectl get --namespace {{ .Release.Namespace }} svc -w {{ include "metaflow-service.fullname" . }}'
+  NOTE: It may take a few minutes for the LoadBalancer IP to be available.
+        You can watch the status of by running 'kubectl get --namespace {{ .Release.Namespace }} svc -w {{ include "metaflow-service.fullname" . }}'
   export SERVICE_IP=$(kubectl get svc --namespace {{ .Release.Namespace }} {{ include "metaflow-service.fullname" . }} --template "{{"{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}"}}")
-  echo http://$SERVICE_IP:{{ .Values.service.port }}
+  if [ -z "$SERVICE_IP" ]; then
+    echo "Error: Unable to retrieve LoadBalancer IP."
+  else
+    echo http://$SERVICE_IP:{{ .Values.service.port }}
+  fi
 {{- else if contains "ClusterIP" .Values.service.type }}
   export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "metaflow-service.name" . }},app.kubernetes.io/instance={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}")
   export CONTAINER_PORT=$(kubectl get pod --namespace {{ .Release.Namespace }} $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
-  echo "Visit http://127.0.0.1:8080 to use your application"
-  kubectl --namespace {{ .Release.Namespace }} port-forward $POD_NAME 8080:$CONTAINER_PORT
+  if [ -z "$POD_NAME" ] || [ -z "$CONTAINER_PORT" ]; then
+    echo "Error: Unable to retrieve Pod name or Container port."
+  else
+    echo "Visit http://127.0.0.1:8080 to use your application"
+    kubectl --namespace {{ .Release.Namespace }} port-forward $POD_NAME 8080:$CONTAINER_PORT
+  fi
 {{- end }}