Alfresco Content Services (ACS) is an Enterprise Content Management (ECM) system that is used for document and case management, project collaboration, web content publishing, and compliant records management. The flexible compute, storage, and database services that Kubernetes offers make it an ideal platform for Alfresco Content Services. This helm chart presents an enterprise-grade Alfresco Content Services configuration that you can adapt to virtually any scenario with the ability to scale up, down or out, depending on your use case.
The Helm chart in this repository supports deploying the Enterprise or Community Edition of ACS.
The Enterprise configuration will deploy the following system:
The Community configuration will deploy the following system:
Alfresco provides tested Helm charts as a "template" to accelerate deployment and configuration for customers who want to take advantage of Kubernetes orchestration capabilities. Please remember that as stated in our support policies, similarly to other deployment artifacts, they are not meant to be used 'as-is' in production. Our goal is to save you time and effort deploying Alfresco Content Services for your organization.
Out of the box we provide a working ACS installation by configuring a PostgreSQL database via Bitnami charts and an ActiveMQ message broker with a simple activemq subchart, both with basic authentication and without any kind of redundancy.
You typically want to disable the embedded postgres and activemq broker and connect directly to managed instances of those services. Another typical change would be the integration of your company-wide monitoring, logging and backup solutions.
If you want to have additional JDBC drivers available or to extend the default ACS functionalities, you are required to build custom Docker images, deploy them on a public/private registry and set the appropriate values in the charts.
For example, you can override the ACS repository image by specifying in the values:
repository:
image:
repository: registry.example.org/my-custom-alfresco-content-repository
tag: 7.3.0See the registry authentication page to configure credentials for your private registry.
Helm charts values contains secrets to be set. For deployment in sensitive environments please see the Security page before proceeding with the installation.
For the best results we recommend deploying ACS to AWS EKS. If you have a machine with at least 16GB of memory you can also deploy using Docker for Desktop.
The recommended cluster resources for the Enterprise version with the components enabled by default are: at least 3 nodes with 12 cpu cores and 32 GB of memory in total. You can install with lower requirements by fine tuning the resource requests available in the values for each component.
There are also several examples showing how to deploy with various configurations:
- Deploy with AWS Services (S3, RDS and MQ)
- Deploy with Intelligence Services
- Deploy with Microsoft 365 Connector (Office Online Integration)
- Enable access to Search Services
- Enable Email Services
- Use a custom metadata keystore
- Install ACS license as part of the deployment
You can use the standard helm upgrade acs ./alfresco/alfresco-content-services --reuse-values command, but make sure you read the upgrades page
to learn about breaking changes that may have been introduced since previous
helm charts versions.
An autogenerated list of helm values used in the chart and their default values can be found here: Alfresco Content Services Helm Chart
Since the Alfresco Content Services chart also has local chart dependencies you can find the list of values that can be configured for these charts in their respective base folder:
- Alfresco ActiveMQ Helm Chart
- Alfresco Search Helm Chart
- Alfresco Insight Zeppelin Helm Chart
- Alfresco Sync Service Helm Chart
To customise the Helm deployment, for example applying AMPs, we recommend following the best practice of creating your own custom Docker image(s). The Customisation Guide walks you through this process.
The easiest way to troubleshoot issues on a Kubernetes deployment is to use the Lens desktop application, which is available for Mac, Windows and Linux. Follow the getting started guide to configure your environment.
Alternatively, the traditional Kubernetes dashboard can also be used. Presuming you have deployed the dashboard in the cluster you can use the following steps to explore your deployment:
-
Retrieve the service account token with the following command:
kubectl -n kube-system describe secret $(kubectl -n kube-system get secret | grep eks-admin | awk '{print $1}') -
Run the kubectl proxy:
kubectl proxy & -
Open a browser and navigate to:
http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/#/login -
Select "Token", enter the token retrieved in step 1 and press the "Sign in" button
-
Select "alfresco" from the "Namespace" drop-down menu, click the "Pods" link and click on a pod name. To view the logs press the Menu icon in the toolbar as highlighted in the screenshot below:
This approach allows to connect to a specific application in the cluster. See kubernetes documentation for details.
Any component of the deployment that is not exposed via ingress rules can be accessed in this way, for example Alfresco Search, DB or individual transformers.
Log files for individual pods can also be viewed from the command line using the kubectl utility.
Retrieve the list of pods in the alfresco namespace by using the following command:
kubectl get pods -n alfrescoThen to retrieve the logs for a pod using the following command (replacing the pod name appropriately):
kubectl logs acs-alfresco-cs-repository-69545958df-6wzl6 -n alfrescoTo continually follow the log file for a pod use the -f options as follows:
kubectl logs -f acs-alfresco-cs-repository-69545958df-6wzl6 -n alfrescoIf you wish to change the log levels for a specific Java package or class in a running content-repository these can be changed via the Admin Console. However, please be aware that the changes are applied only to one content-repository node, the one from which the Admin console is launched. Use the following URL to access the log settings page: https://<host>/alfresco/service/enterprise/admin/admin-log-settings
To add additional repository log statements across the whole cluster use the extraLogStatements property via the values file as shown in the example below:
repository:
...
extraLogStatements:
org.alfresco.repo.content.transform.TransformerDebug: debug
org.alfresco.repo.security.authentication.identityservice: debugNOTE: ACS deployment does not include any log aggregation tools. The logs generated by pods will be lost once the pods are terminated.
This tool allows you to download a ZIP file containing information useful for troubleshooting and supporting your system. Issue a GET request (Admin only) to: https://<host>/alfresco/service/api/admin/jmxdump