Kubernetes deployment

Install using the Helm chart

The MDSSC k8s deployment can be performed directly using the provided helm chart in our public GitHub repo here and example configuration files for different environments are provided in the helm_charts directory.

For system requirements and sizing considerations, please refer to the Sizing Guide | Kubernetes Deplyoment.

Using the helm repository

The GitHub repository can be used directly as a helm repo:

Bash
Copy

Or the repository can be cloned locally:

Bash
Copy

Storage

MDSSC containers are stateless and don't require any persistent storage. If the MongoDB database is deployed in the cluster, then it's recommended to use persistent storage managed by a cloud provider. The external database can be configured from the values:

YAML
Copy

When using an external database that is not deployed from the MDSSC chart, the deploy_with_mdssc_db value has to be set to false in order to not deploy an additional database from the chart.

Exposing MDSSC

By default, the helm chart deploys a ClusterIP service for MD Core and this can be changed to any service type supported by the Kubernetes cluster. For example, a LoadBalancerservice type can be created by overwriting the service_type value in the webclientcomponent:

YAML
Copy

MDSSC can also be exposed using an ingress:

YAML
Copy

##

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard