Helm Charts /Kubernetes
This is an advanced setup. This article is intended for experts who already have experience of working with Kubernetes and Helm Charts. Other deployment options besides Kubernetes are also possible, including, but not limited to:
onPrem: Podman, Docker
Cloud: Azure Container Apps, S3 ECS (Fargate)
The kgs container products are compatible with Kubernetes environments. Please refer to the following link for information on supported Kubernetes versions: Prerequisites for tia® and kgs Software Components | Container based deployment
Due to the complexity of Kubernetes deployments kgs offers a Helm chart that serves as a template to assist in implementing the products.
Please be aware that the template is not ready for production. It must be changed by the customer to meet their requirements for their environment so that it can be used in production. Kgs make sure that the software in the container and there respective interfaces are compatible. It is not necessary nor intended to apply Helm chart updates on a regular basis.
Helm charts templates are available in nexus an can be downloaded there as a Zip package.
tia® Core helm chart templates:
tia® ContentServer https://nexus.kgs-cloud.de/#browse/browse:helm-hosted:tiacore contains Content Servers for these interfaces
ArchiveLink (saphttp)
ILM
CMIS
In the package the values yaml is a starting point for configuration. Make sure your provided username and password is configured. Make sure the latest tia® Core version is used for the images: tia/core/cmis, tia/core/ilm,tia/core/saphttp.
The provided tia® Core license need s to be added to config\license\license-core.json. Repository configuration is in the folder config\repository-config for each interface. Not part of the configuration is any volume mount or external storage configuration.
tia® products helm chart templates:
tia® Products https://nexus.kgs-cloud.de/#browse/browse:helm-hosted:kgs-osgi-products contains
tia® Viewer Core
tia® Webservice
In the package the values yaml is a starting point for configuration. Make sure your provided username and password is configured. Make sure the latest tia® Core version is used for the images: tia-viewer/archivelink-oidc, tia-webservice/tia-webservice.
The license is in config\license is only for the tia® Viewer. The webservice accepts a license in the KGSWebUi.