Use this Helm charts to provision CKEditor Collaboration Server on your Kubernetes cluster.
Note: This script uses Helm. If you haven't worked with it before, we highly recommend getting familiar with it first: https://helm.sh/docs/intro/quickstart/
Short description of every helm chart in this directory:
Helm chart containing the resources to run CKEditor Collaboration Server configured to connect to external third-party services.
Fast way to provision whole infrastructure needed for CKEditor Collaboration Server. Used charts as dependencies:
ckeditor-csbitnami/mysqlbitnami/redis
⚠️ Not for production purposes! This configuration is insecure, not persistent and its purpose is testing only.
Helm chart containing the resources to run CKEditor Word Services Server which contains Import from Word and Export to Word features.
Helm chart containing the resources to run CKEditor PDF Converter Server which contains Export to PDF.
Helm chart containing the resources to run CKBox configured to connect to external third-party services.
Fast way to provision whole infrastructure needed for CKBox . Used charts as dependencies:
ckboxbitnami/mysqlbitnami/redis
⚠️ Not for production purposes! This configuration is insecure, not persistent and its purpose is testing only.
Follow instructions from helm charts:
Easier configuration management can be achieved by creating separate based on
ckeditor-cs/values.yaml configuration file. It can be passed to helm install
by -f [path] flag.
⚠️ If you want to store configuration: Make sure your environment variables are secure before saving them in external service. You can use SOPS for encrypting specific parts of yaml file.
Environment variables mentioned in the configuration file are an absolute minimum to run the service. Visit documentation for the whole list of configuration options:
An individual instance of the CKEditor Collaboration Server container.
Manages provisioning, creating, replacing and scaling pods.
An abstract object that exposes a specific set of pods as a network interface. That set if pods targeting is determined by selectors assigned to them.
Ingress manages external access to the service located in the cluster. Creates routing by hostnames and can handle terminating SSL/TLS.
Automatically enabled authenticator in Kubernetes. Uses signed bearer tokens to verify requests. Bearer tokens are mounted into pods.
Storage and management of sensitive information. In this use case, the environment variables passed to the pods.
You can clean remove installed deployment from Kubernetes by running helm delete ckeditor-cs command.