Support Ticket Status

All Cloud 66 customers can now track progress of their support tickets, as well as see a list of their previous support tickets under the Support link on the dashboard. As your ticket moves around within Cloud 66 (1st Line support, 2nd line escalation, etc) it will be updated on this page so you can keep track of its progress.

To see this page, click on the Support link on top of your dashboard.

Service Accounts

Today I am excited to announce general availability of Service Accounts. Service Accounts are like team members that cannot login to the UI. They can be used to setup automation or notifications that are not bound to a real person.

If you use notifications like Slack for your Cloud 66 applications, you probably want to limit them to a single notificaiotn per event. More importantly, you would like your notifications and API integrations not to be linked to a real person, so they won't break when they leave your team. Service Accounts are perfect for that: Setup a Service Account and use them to enable notifications, CX (Toolbelt) or API integrations as you would with a real team member.

You can find more information about Service Accounts on our blog

Maestro Repair Options

There are some scenarios in which your Kubernetes cluster could become unavailable. The most common cause of this issue is a cluster with a single master that runs out of memory or gets locked into scheduling services that are utilizing all of its available resources. This can cause processes to be killed, the cluster to become unreachable, and, in the worst cases, corrupt the master. The fastest way to resolve this is to repair your cluster, essentially reinitializing it as new.

Now, if you're faced with this scenario, you can run the repair operation yourself! We've replaced our deploy-with-options overlay with a side-drawer component which gives us some more space to work with. Take a look at our help documentation for more on this new option!

Maestro Bulk Deletes

We now support scaling down (deletion) of multiple maestro worker nodes at once. We already support this for Rails/Rack servers, so this update brings Maestro stacks in-line. This feature is particularly useful for users with larger clusters who are looking to resize or rotate the servers!

Rails Default Node Version Update (#2)

As announced two weeks ago, we have now changed the default Node version that is installed on newly created Rails/Rack servers to v10.x. Don't hesitate to drop us a message on slack or email if you have any questions or feedback about this!

Updated Linode Regions

We've just added two more regions to Linode (Sydney and Mumbai). If you were waiting for these, wait no longer!

Maestro Service Node Allocation

I am very happy to announce that Maestro now supports service node allocation. Using your service.yml configuration you can now specify which servers you want your service to run on. This is useful when servers in your cluster are not all equal, or you need to separate specific services.

You can choose to specify a list of server names, or matching server tags, to determine the servers. The default behavior is unchanged, and if not specified, services will still run on any/all of the available servers. If no servers match your required constraints, the service will not be scheduled. For more information and to get started, best place is the help documentation!

AWS ELB/ALB SSL Policy

Pleased to announce that any AWS ELBs/ALBs created from now onward will default to using a more secure set of SSL protocols and ciphers (when performing SSL termination). Existing ALB/ELBs can have their policies manually modified via the AWS UI. In the unlikely case that you need to specify a less secure protocol or cipher, you can use your manifest to specify the policy you want.

Rails Default Node Version Update

This is an advance notice that in two weeks (from the week starting 10th August) we will be changing the default Node version installed on newly created Rails/Rack servers to v10.x. Although this isn't the latest Node version, it still caters best to users with older Rails applications.

For newer (or older) Node versions, users can still use their manifest to specify the version they require. For more information and examples of this, see the help page on controlling your Node version.

Bulk Env-Vars API Endpoints

Pleased to announce that now available are new API endpoints for uploading and downloading environment variables in bulk. We know that some users have been waiting patiently for this, so very happy to make it public.

We've also created the corresponding commands within the cx toolbelt, so check out the Cloud 66 help docs for bulk downloads and bulk uploads!