Page Comparison

...

1. Add the helm repository

   Code Block
   $ 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:

   Code Block

   $ helm search repo -l mz10/usage-engine-private-edition --version <chart version> Example: $ help search repo -l mz10/usage-engine-private-edition \ —version 10.6.0-release-20210930154327-270ad83673d #The output: NAME CHART VERSION APP VERSION DESCRIPTION mz10/usage-engine-private-edition    10.6.0-release-20210930154327-270ad83673d    usage-engine-private-edition mz10/usage-engine-private-edition-ec 10.6.0-release-20210930154327-270ad83673d    usage-engine-private-edition Execution Context

   
   

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

   Info
   title 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 desktopOnline.ecd.nodeHostSelectionEnabled
   -  mzOperatoroperator.rbacAuthProxy.enabled

...