This commit introduces several significant changes to the Paperless AI
Helm chart:
- Updated the version from 0.5.0 to 0.6.0 in `Chart.yaml` to reflect
the new additions.
- Added a new template `paperlessApiSecret.yaml` to define a Kubernetes
Secret for the Paperless API token. This allows secure storage of the
API token, which is now a required value for communication with the
Paperless application.
- Introduced a new function in `_helpers.tpl` called `generateEnv`
that dynamically generates a `.env` file from various configuration
values in `values.yaml`. This includes settings for the Paperless API
URL, AI provider, tagging options, scanning intervals, and more.
- Updated `values.yaml` to include necessary configurations for the
Paperless API, OpenAI, and other related settings, making it easier
for users to configure the chart per their requirements.
- Adjusted resource limits and initial probe delays for improved
performance and quicker health checks.
These enhancements provide better configurability and facilitate
secure management of sensitive credentials, thereby improving user
experience and application reliability.
This commit updates the version of the Paperless AI Helm chart from
0.4.0 to 0.5.0 to reflect new changes and improvements. The PUID
and PGID environment variables have been changed from 1027 and 100
to 1000 and 2000, respectively, to better accommodate user and
group permissions.
Additionally, the resource requests and limits have been adjusted
to specify CPU and memory requirements (100m CPU and 128Mi memory),
ensuring that the container operates within defined resource
constraints. This change enhances performance and stability, making
the chart more suitable for various deployment environments.
No breaking changes were introduced, but users should verify their
permissions align with the new PUID and PGID settings.
This commit updates the version of the Helm chart for Paperless AI from
0.3.0 to 0.4.0 to reflect the latest changes and improvements.
Additionally, unnecessary resource allocations in the
deployment.yaml file have been removed, particularly
the commented-out section related to resources. This
cleanup enhances readability and maintainability of the
chart's deployment configuration.
No breaking changes were introduced, but it simplifies the
environment variable section to improve clarity.
Updated the Paperless AI Helm chart to version 0.3.0 to reflect
the latest changes and improvements. Modified the deployment.yaml
by adding liveness and readiness probes, which enhance the
resilience and monitoring of the application by checking its
availability and readiness to serve traffic.
Additionally, adjusted the values.yaml file to set the service
account creation to false and commented out the PUID and PGID
environment variables for increased flexibility and to avoid
potential permission issues during deployment. Note that the
securityContext settings for the Pod and Container have also
been changed to disable the pod's user/group settings, which
may affect how the application interacts with resources.
Bumped the version of the Paperless AI Helm chart from 0.1.0 to 0.2.0 to
reflect the latest updates. Various templates have been modified for
improved consistency and adherence to best practices.
Notable changes include:
- Removal of unnecessary comments in `pvc.yaml` for a cleaner
look.
- Simplification of indentation and formatting in `ingress.yaml`,
`pvc.yaml`, and `service.yaml` to ensure correct rendering of
Kubernetes resources.
- Fixed comments in templates to clarify their purpose while
removing inline comments for a streamlined approach.
These changes enhance maintainability and clarity within the
Helm chart templates. No breaking changes are introduced in this
update.
The version number in the Chart.yaml file has been changed from
0.2.0 to 0.1.0 to reflect the correct versioning of the paperless-ai
chart. This adjustment is necessary to avoid confusion regarding version
compatibility and ensure proper deployment practices.
Additionally, the service.yaml template has been refined to correct the
spacing in the service name and labels. Previously, there were extra
spaces around the include function calls, which could lead to
rendering issues in the generated Kubernetes manifests.
These changes are crucial for maintaining accurate versioning and
preventing potential application deployment errors. No breaking changes
are introduced in this update.
Updated the version number in the Chart.yaml file for the
paperless-ai Helm chart from 0.1.0 to 0.2.0. This change was made
to reflect the latest updates and improvements made to the chart,
ensuring users are aware of the new version. No breaking changes
were introduced with this update, and the appVersion remains at
3.0.7.
Updated the service.yaml template by removing unnecessary comments and
whitespace for better readability. The updates include cleanup of the
Kubernetes service definition while maintaining the original functionality.
These changes simplify the code structure without altering the service's
behavior. No breaking changes were introduced, ensuring compatibility with
existing configurations.
This update substantially refactors the paperless-ai Helm chart.
Key changes include:
- Complete removal of outdated files: `.helmignore`, `LICENSE`,
`README.adoc`, and several template files like `configfileConfigmap.yaml`,
`configmap.yaml`, `dataPvc.yaml`, `envfileSecret.yaml`,
`openAiApiSecret.yaml`, `paperlessApiSecret.yaml`, and others.
- Introduction of a new Persistent Volume Claim configuration in
`pvc.yaml` to simplify storage management.
- Significant updates to `Chart.yaml` for better metadata, including
a new maintainer and project description in German.
- Enhancements to the main deployment template in `deployment.yaml`,
focusing on clarity and proper utilization of Kubernetes security
contexts, environment variables, and container properties.
- Updated service definitions in `service.yaml` with better labels
and service properties.
- Refined the `ingress.yaml` to improve external service access
management, including annotations for potential customization.
These changes were implemented to modernize the Helm chart based on
the current best practices, improve user experience, and set a
foundation for future enhancements. There are no breaking changes to
the existing user configurations.
Updates the Paperless-AI Helm chart version from 0.1.0 to 0.7.0 and the
application version from 2.1.3 to 3.0.7. This significant version jump
reflects major improvements in the underlying application including new
features and stability improvements. This update ensures the chart
references the latest stable release of Paperless-AI.
This commit restructures the paperless-ai Helm chart by moving all files
from the nested directory (charts/paperless-ai/paperless-ai/) to the
standard Helm chart directory structure (charts/paperless-ai/). The change
eliminates the redundant directory nesting that was causing issues with
Helm chart packaging and installation. No functional changes were made to
any files - this is purely a directory structure reorganization to follow
Helm best practices and improve chart maintainability.
This commit introduces a new Helm chart for deploying paperless-ai, an AI-
enhanced document management system based on paperless-ngx. The chart
includes:
- Complete deployment configuration with configurable replicas
- Persistent volume support for data storage
- Secret management for API tokens and keys
- Environment variable configuration via ConfigMaps and Secrets
- Ingress configuration options
- Support for both OpenAI and Ollama AI providers
- Customizable system prompts and document processing settings
- CI workflow for automated chart packaging and publishing
The chart enables Kubernetes users to easily deploy and configure the
paperless-ai system with proper separation of configuration and secrets.
Bump Excalidraw chart version and update image tag
Updated the chart version from 1.0.1 to 1.0.2 to reflect the latest
changes in our configuration. Additionally, modified the image
tag in the values.yaml file to "latest" to ensure that the most
recent version of the Excalidraw image is pulled when deploying.
This small change aims to facilitate easier updates for users
and guarantee that they have access to the latest features and
bug fixes. Please note that using "latest" may have implications
for reproducibility in deployments.
```
Update Excalidraw Helm chart to version 1.0.1
This commit updates the Excalidraw Helm chart's metadata, changing
the appVersion from 0.17.6 to 0.18.0 and the chart version from
1.0.0 to 1.0.1. These changes reflect an update to the application
version to ensure compatibility with new features or fixes.
Additionally, in the deployment configuration, the container port
is now set directly to 80 instead of using a default provided by
the service values. This change simplifies the deployment
configuration and ensures that the container listens on the
expected port regardless of service value changes.
```
Update excalidraw Helm chart values for clarity
Modified the values.yaml file for the excalidraw Helm chart
to enhance clarity and configuration consistency. Specific
changes include setting defaults for undefined values
such as image tag, pod security context, and resources,
ensuring that users can easily identify where to fill in
custom configurations. This update aims to prevent confusion
for users who might overlook required values due to empty
fields, thereby improving the overall user experience and
configuration process.
```
Add Helm chart for Excalidraw deployment
This commit introduces a complete Helm chart for deploying
Excalidraw, a virtual whiteboard for sketching diagrams, on
Kubernetes. The chart includes essential templates for
deployment, service, ingress, horizontal pod autoscaler,
and service account, along with a README and values
configuration. Key features include customizable image
repository, resource requests, autoscaling support, and
ingress configuration options.
These changes facilitate easier deployment and management
of Excalidraw in Kubernetes environments, providing
users with a structured approach to configure their
installations. No breaking changes are introduced.
```
