v1.5.0: Prometheus monitoring support
Breaking Changes
In this release we unified how you should specify resources for browser images in browsers.json
and service images in service.json
files. You can now specify requests
and limits
in service.json
file as follows:
Before:
{
"images": {
"logger": {
"image": "my-registry.example.com/moon/logger:latest-release",
"cpu": "0.3",
"mem": "1024Mi"
}
}
}
Now:
{
"images": {
"logger": {
"image": "my-registry.example.com/moon/logger:latest-release",
"resources": {
"limits": {
"cpu": "0.3",
"memory": "1024Mi"
},
"requests": {
"cpu": "0.3",
"memory": "1024Mi"
}
}
}
}
}
Security Changes
In previous releases all browsers pods by default were created with SYS_ADMIN
Linux kernel capability. To work in restricted environments starting from this release by default browser pods are created without this capability. This change mainly influences working with Chromium-based browsers. You have two options:
Option 1. Configure Moon to continue running all browser pods with SYS_ADMIN
kernel capability. To have this option - just add the following to Moon service.json
configuration file:
{
"kernelCaps": [ "SYS_ADMIN" ]
}
This is what we do by default in our official deployment manifests.
Option 2. Start Chrome with --no-sandbox
flag from your test code.
Known Update Issues
When doing a rolling update from 1.4.x series you can see the following messages in moon-api
log:
2020/05/21 14:54:45 [STATUS_REQUEST_ERROR] [127.0.0.1] [parse enableVideo: strconv.ParseBool: parsing "": invalid syntax]
These messages will disappear as soon as browser pods created by 1.4.x are deleted.
New Features
- #128 - ability to configure service account name
- #139 - Prometheus monitoring support
- #166 - showing
enableVideo
in/status
API - #205 - ability to override
requests
andlimits
for service images separately