Maestro users can now use a specific volume syntax to allow the generation of a Kubernetes Secret (or Kubernetes ConfigMap) with automated mounting to a path inside service containers, making them available in a local folder your service application. You the contents of which are automatically generated from your application ConfigStore or Environment Variables.
If you want to learn more, see our help page: Adding Secret and/or ConfigMap storage volumes
Cloud 66 Toolbelt (CX) now supports Apple Silicon (M1 CPU). You can download the right version from https://app.cloud66.com/toolbelt
I am pleased to announce that we now have native support for disk space alerts. You can register for disk alert notifications via your application's notifications page (along with the other application notifications).
You can also define a threshold for when you want to be alerted per server (the default threshold is set at 80% disk usage). For more information please see our disk space alerts documentation.
Ruby 3 was released, as promised, on the 25th of December. This is a major release of Ruby with many improvements all, most of which are around performance.
Today, we added Ruby 3 support for all Cloud 66 customers, just before heading off to a locked down New Years celebration online!
We hope you enjoy using Ruby 3 on your own applications.
Rails application users can now elect to use a version of Ruby precompiled with jemalloc. To use this, you can specify your memory_allocator via your manifest. Once specified via your manifest, you can then scale up new application servers, or if downtime does not concern you, "deploy-with-options" selecting "Apply Ruby Upgrades".
We have found jemalloc to be helpful with memory bloat in our own application. There are a lot of articles out there about it like this one.
As always, please be sure to test first in your non-production environment. Happy memory taming!
We now optionally allow you to run your rake tasks and/or server jobs as the nginx user. This is particularly useful for when you need to create files or assets to be consumed by your web application (as your web application runs as the nginx user). For more about these please see our rake job and server job documentation.
You can now use startup health checks in your Maestro application service configurations. This applies the underlying Kubernetes "startupProbe" configuration to your workloads. Note that this will only be applied on applications running Kubernetes v1.16 or greater.
For more about this health check type, and when to use it, please see our health check documentation.
We are continuing to make UX improvements to the scale-up user interface. Replacing our older "modal style" overlays with our "drawer component". The additional vertical space available allows us to make further improvements to form usability, keeping in-line with the most recent form design guidelines. Let us know what you think when you next scale up a server!
The server metadata endpoint now reports the version of your code that has been deployed. To use this in your own workflows, you can use curl and jq to extract the relevant bits of information you need. Check out some workflow examples in our help documentation!
All environment variable names are now listed in the audit record of their change. Previously, only the change was mentioned in the audit record without listing the names of the changes environment variables. This is now improved to provide more clarity.
