deployment:
+ replicas: 3As you could see above Helm chart is the recommended Moon installation way for both Kubernetes and Openshift. Our Helm chart comes with recommended defaults that will work out of the box in most cases. However, there are situations when you wish to install Moon with some advanced features already activated and to be able to easily reproduce the same installation later. For example, by default Moon does not record videos of browser sessions, and you may need this in your processes. Similarly, you may want to launch browsers in multiple namespaces or use additional trusted TLS certificates.
+Although, all these features can be activated just by manually editing respective Moon objects (configuration object, browsers set, devices set) with kubectl edit command, such changes will be overwritten by Helm during the next deployment. Helm provides better way of having reproducible deployment configuration state - values files. It works like this:
Every Helm chart has default settings stored in values.yaml file and distributed with all the rest of chart files. For example, an up-to-date values.yaml file for Moon 2.x Helm chart is stored here. This file contains reasonable defaults.
If you need to change some defaults to custom values, you create a local values.yaml file containing only the values you wish to change. For example, in Moon Helm chart number of Moon replicas can be set using deployment.replicas field in values.yaml. You create a text values.yaml file like this:
deployment:
+ replicas: 3Such file should be stored under your preferred version control system. This guarantees - you will never lose your custom deployment settings.
+To apply your custom settings while (re)deploying Moon - simply pass full path to your values.yaml file in Helm command:
$ helm upgrade --install -f path/to/values.yaml -n moon moon aerokube/moon2Overriding some parameter in values.yaml is equivalent but more useful than providing the same key as --set flag, e.g.:
$ helm upgrade --install --set deployment.replicas=3 -n moon moon aerokube/moon2Moon 2.x configuration is stored as native Kubernetes objects called custom resources:
+Quotas - containing all configuration specific to one Moon user.
+Configuration Objects - storing various configuration options.
+Browser Sets - storing browsers startup configuration.
+Devices Sets - providing information about available mobile devices for mobile emulation.
+Licenses - storing installed Moon license keys.
+Our Helm chart contains a dedicated key in values.yaml corresponding to every such resource:
quota: # Stores a list of quotas
+ quota1:
+ # Quota1 specification
+ quota2:
+ # Quota2 specification
+
+configs: # Stores a list of configuration objects
+ config1:
+ # Config1 specification
+ config2:
+ # Config2 specification
+
+browsers: # Stores a list of browsers sets
+ browsersset1:
+ # Browsersset1 specification
+ browsersset2:
+ # Browsersset2 specification
+
+license: # Stores Moon license key (currently only one license key is supported in Helm chart)As you can see for all resources except licenses you can define multiple different instances: multiple configuration objects, multiple quota objects and multiple browsers sets. Every field you set in resource specification is converted as is to a Kubernetes custom resource. For example, consider the following browsers set in values.yaml:
browsers:
+ my-browserset:
+ selenium:
+ firefox:
+ repository: quay.io/browser/firefox
+ chrome:
+ repository: quay.io/browser/chromeWhen you apply Helm chart with the following definition in values.yaml, it will be automatically converted to browsers set Kubernetes resource like this:
+apiVersion: moon.aerokube.com/v1
+kind: BrowserSet
+metadata:
+ name: my-browserset
+ namespace: moon # Your namespace name for Moon will be here
+spec:
+ selenium:
+ firefox:
+ repository: quay.io/browser/firefox
+ chrome:
+ repository: quay.io/browser/chromeIf you create multiple entries in the list of browsers sets in values.yaml, then multiple Kubernetes resources will be created.