doc: helm charts documentation

[Grraahaam]

Description 📣

Note

I know there's a lot of addition, but it's mostly auto-generated. Schemas and documentation ✌🏽

Documentation was missing for the new infisical-standalone chart, and previous helm charts documentations were a bit outdated. This PR aims to resolve this.

What have been done:

• ✅ implement helm-docs instead of the previous automated documentation generator

  • used gotemplates for DRY and automation purposes
  • generated the charts' documentation

• ✅ implement helm-schema to automatically generate YAML validation schema for Helm

  • as for today the schema is pretty permissive, to avoid any issues with the current developers
  • not yet implemented in helm-docs: [Enhancement] Also use values.schema.json norwoodj/helm-docs#90

• ✅ set the infisical service port to 80 instead of 8080 (standard port for http)

  • to avoid thinking about the port when trying to use the service's URL in-cluster (e.g. self-hosted + operator)

• ✅ add license to each of the charts, aiming to be used one day by either cloudsmith/artifact.io... (common in other helm charts)

• ✅ add alternative for the developers to define their infisical configuration directly through helm with infisical.config.<CONFIG_KEY>

  • it allows developers using gitops mechanism to easily provide every variables in a normalized way through the same tool
  • but of course we're keeping the other alternatives like infisical-secrets to provide the same variables
  • order of precedence is now: infisical.config > infisical.secrets > default (e.g. for postgres and redis)
    • https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#container-v1-core
  • post discussing about benefits between env: and envFrom:: https://flagzeta.org/articles/difference-between-env-and-envfrom-kubernetes-deployments/

• ✅ deprecate the infisical (mongodb) chart

• ✅ update all the Chart.yaml to be a bit more complete

  • those additional keys help the registries to scan your chart correctly and provide accurate information to the developers

• ✅ remove and rename some redis keys not found in the remote chart

  • https://github.com/bitnami/charts/blob/main/bitnami/redis/values.yaml
  • usePassword doesnt seems to be available and have been replaced by auth.enabled
  • cluster.enabled doesnt exist and have been removed (as its a complete different chart in Bitnami's repo)

• ✅ merge postgres persistence common settings to current values.yaml

  • if the developer wants to increase the PVC size for example

---

BTW we might need to update the old deprecated images on https://hub.docker.com?

• add deprecation warning on front/backend images
  • https://hub.docker.com/r/infisical/backend
  • https://hub.docker.com/r/infisical/frontend

---

Some resources about schema validation:

• https://objectpartners.com/2021/01/21/why-we-started-using-json-schema-in-our-internal-helm-charts/
• https://austindewey.com/2020/06/13/helm-tricks-input-validation-with-values-schema-json/

Type ✨

• New feature
• Documentation

Tests 🛠️

You can follow the doc provided in this PR, everything is explained. Let me know if you need further explanations

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[Grraahaam]

Description updated for readability and to provide more resources explaining some choices

[Grraahaam]

Hey @maidul98, any chance you get some time to review this PR? Want me to fix the conflicts already?