DOCSEARCHbyAlgolia
Submit Docs

Community Charts Documentation

website·Indexed 30 days ago

https://community-charts.github.io

Release notes and update logs for community-maintained Helm charts, including versions for Actual Budget, Cloudflared, MLflow, Drone, Outline, pypiserver, and n8n.

Tokens
98.8K
Snippets
609
Records
833
Agent score
75%

What's inside Community Charts

  2. What is new in actualbudget Helm chart v1.9.0

    The actualbudget Helm chart version 1.9.0 (deploying app version 26.6.0) introduces several security and stability improvements for Kubernetes deployments. Key updates include support for immutable image pulls via optional image digests, the enablement of readOnlyRootFilesystem with a built-in tmp emptyDir volume for better security, and corrections to secret namespace handling to ensure the release namespace is used.

  5. Enterprise features of the MLflow Helm chart

    The MLflow chart is designed for production and enterprise environments, offering the following capabilities:

    • Backend Database Support: Compatible with PostgreSQL, MySQL, and SQLite.
    • Cloud Storage Integration: Supports AWS S3, Google Cloud Storage (GCS), and Azure Blob Storage for artifact storage.
    • Enterprise Management: Includes built-in authentication, LDAP integration, and autoscaling support.
    • Lifecycle Management: Handles database schema migrations automatically using init containers.
    • Observability: Integrated with Prometheus via ServiceMonitor for monitoring.

  7. Understand n8n Queue Mode Architecture

    Queue mode enables distributed execution by separating the UI/API from the execution and webhook processing. This is the recommended architecture for production deployments to ensure scalability and reliability.

    Component Roles:

    • Main Node: Handles the User Interface (UI), API requests, and workflow management.
    • Worker Nodes: Execute workflows and process tasks.
    • Webhook Nodes: Process incoming webhook requests.
    • Redis: Acts as the message broker for communication between all nodes.

  8. Configure PostgreSQL High Availability (HA) for n8n

    For production environments requiring high availability and read scaling, use the replication architecture in the PostgreSQL configuration.
    db:
  type: postgresdb

postgresql:
  enabled: true
  architecture: replication  # Enable replication
  auth:
    username: n8n
    password: your-secure-password
    database: n8n
  primary:
    persistence:
      enabled: true
      size: 20Gi
    service:
      type: ClusterIP
  readReplicas:
    persistence:
      enabled: true
      size: 20Gi
    resources:
      requests:
        cpu: 100m
        memory: 256Mi
      limits:
        cpu: 500m
        memory: 512Mi

  9. Understand Actual Budget storage architecture

    Actual Budget organizes its data into two primary directories under the base data path:

    • /data/server-files/: Contains server configuration and the account.sqlite database.
    • /data/user-files/: Contains budget files and user data (stored as .blob files).

  10. Set up High Availability (HA) Redis for n8n

    Enable HA Redis by setting the architecture to replication (master-slave). This configuration allows for a master node and multiple replicas to ensure the message bus remains available.
    redis:
  enabled: true
  architecture: replication  # Master-slave replication
  master:
    persistence:
      enabled: true
      size: 10Gi
    resources:
      requests:
        cpu: 100m
        memory: 256Mi
      limits:
        cpu: 500m
        memory: 512Mi
  replica:
    replicaCount: 2
    persistence:
      enabled: true
      size: 10Gi
    resources:
      requests:
        cpu: 100m
        memory: 256Mi
      limits:
        cpu: 500m
        memory: 512Mi