📝 feat: Update README with feature list and deployment instructions

refactor: Remove old Helm chart files and templates

feat: Add new Helm chart structure for neo-blog deployment

chore: Add .helmignore and initial Chart.yaml for Helm chart

feat: Implement backend and frontend deployment templates in Helm chart

feat: Create services and ingress configurations for backend and frontend

chore: Define resource limits and requests for backend and frontend in values.yaml

feat: Enable autoscaling configuration for backend and frontend deployments

chore: Clean up unused files and configurations from previous setup

helm/Chart.yaml

@@ -0,0 +1,24 @@
+apiVersion: v2
+name: neo-blog
+description: A Helm chart for Kubernetes
+
+# 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: "latest"