Skip to main content

Build a test-install

How to create a "sandbox" test-installation.

All_in install without Kobil license - hosted as single deployment (as a "sandbox") for simple testing purposes only

  • main parameter for test-install in the deployment configuration file "values.yaml" is (ssms:certificate:testInstallation) - keep this to testInstallation: true results in a test-installation - which is fixed and could be NOT migrated into a licensed Kobil Service later. With this the CAkeystore passphrase have to be default to "123456".

  • using mBattery to prepare runtime deployments for mPower into the used k8s-cluster providing ingress-controller, databases and/or monitoring, tracing or logging services for the Kobil Services covered by the mPower deployment. This is configurable by mBattery deployment configuration file "values.yaml" per "enabled: true|false" for each component.

Run "helm install" into namespace​

  • ensure to have repository pull-secret created prior to run "helm install" and having helm kobil chart repository access enabled.
  • verify per mbattery readme to implement the requirements first.
  • helm install mbattery -f ./values.yaml kobil/mbattery
  • verify the required DB-services are up and running fine providing the mPower required DB-Services (i.e. mysql for Security Server, postgres + redis for IDP, loki for Grafana).
  • verify per mpower readme to implement the requirements first.
  • helm install mpower -f ./values.yaml kobil/mpower
  • watch "ssms-master-config*" Pod(job) log output to verify access to Security Server-DB is possible.
  • watch "ssms-mgt/svc" Pod log output to verify access to Security Server-DB is possible.
  • watch overall pod startup for keycloak-, ssms-, scp-Pods.

Demo Installation find details/info here.