Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The preparations described below are required to install  using Helm charts and Docker images. Read through the steps below and follow each step before installing.


Fetching and Configuring Helm Charts

You will download the Helm chart with the instructions below:

  • Helm chart: usage-engine-private-edition


When you are required to enter the <chart version>, refer to /wiki/spaces/DRXXE/pages/6194875 for the Helm Chart version required

Helm Charts Installation

The Helm chart configuration installs a large portion of the product, apart from the ECD instance. 

  1. Add the helm repository

    $ helm repo add usage-engine-private-edition 'https://digitalroute-public.github.io/usage-engine-private-edition'
$ helm repo update

  2. Check if the charts are available:

    $ helm search repo -l usage-engine-private-edition/usage-engine-private-edition --version <chart version>
 
Example:
$ helm search repo -l usage-engine-private-edition/usage-engine-private-edition --version 2.0.0

#The output:
		NAME                        						CHART VERSION             	APP VERSION DESCRIPTION                    
 
usage-engine-private-edition/usage-engine-private-edition    	2.0.0    			The Usage Engine Private Edition helm chart                  

  3. f required, modify the Helm chart for the needed level of Access Control for Kubernetes Resources

    Access Control for Kubernetes Resources

     relies on Role Based Access Control (RBAC) when specifying the level of access needed for the kubernetes resources involved in any given  installation. 

    Essentially, to make sure that the service account used has the right level of access in order for  to function properly.
    Some features do require cluster wide access to certain resources (typically resources that are not namespaced). This is realized by the use of ClusterRoles. If ClusterRoles are not permitted in the given kubernetes cluster for one reason or another, those features will have to be switched off.

    The following helm values can be used to switch off features relying on ClusterRoles, see the Helm chart for further details:

    - mzonline.ecd.nodeHostSelectionEnabled
    - mzOperator.rbacAuthProxy.enabled

    Note!

    All information about available properties and values that you may want to update are contained within the Helm chart itself.


Note!

Ensure that there is no firewall rule that restricts access to the exposed ports to the cluster. See Installation (3.0) for more information concerning ports.


  • No labels