Containership 3.10: Multi-Zonal Clusters, Audit Logs, OS Support and More

Containership Kubernetes Engine now supports multiple master node pools across multiple availability zones! CKE clusters have always been able to be configured as highly available (with 3 or more master nodes) but now you can spread those nodes across data centers. As you could imagine there are some complexities that come with this functionality but the team at Containership has simplified the process and gives you the ultimate control on how to set up your clusters.

Multiple Availability Zones for Masters

When you build a cluster with three master nodes that are in the same data center, they are considered highly available. If one node dies, then the others pick up where the controlling master left off. What it does not account for is if the data center itself experiences an outage. In this rare case, your cluster would be out of commission as the master nodes would be unreachable. Now with CKE you can provision your master nodes in different zones, which will allow your cluster to stay functioning in the case of an outage. There are limitations and some small variances between each provider, but the setup has been streamlined in the cluster creation process on Containership.

Vertical Master Scaling

As your business grows so does the infrastructure behind it. Often times you build a cluster with an adequately powered master pool, and several months down the line the number of worker nodes has increased. Now you are at a crossroads where you will need to potentially rebuild your cluster in order to meet the new demands. The ability to vertically scale master nodes helps solve this entirely. Containership can provision new, larger or smaller instances, and then users can sunset the old instances no longer in use. No need to start from scratch! This helps operators optimize their systems and deal with growth in a simple straightforward way.

Centralized Kubernetes Audit Logging

With this feature, Containership will expose every interaction made with the Kubernetes API. Since all users now utilize OIDC for authentication, you will get down to user details on what is being done on the cluster, not just a high level of every interaction. This makes the audit trail more verbose and helps when digging deeper into what is happening on the cluster.

Centralized Cloud Audit Logging

In addition to the Kubernetes Audit trail, we have also started to track all the interactions with the Containership APIs. This covers all users within the organization using the Containership Cloud platform. The trails will explain how your users are utilizing Containership and what changes from a Containership perspective have been made.

Other Notables

We also managed to make some updates to current features with this release. Having the ability to create multiple master pools means you will need to also upgrade multiple pools as new versions are released. Containership Cloud now allows for upgrades to be applied to multiple pools at once, saving you the hassle of doing each one individually. We have also added support for CentOS as the base operating system on all of our supported providers. RedHat Enterprise is also an option for a limited number of our providers.

Want to learn more or have questions? Reach out to the team!

Show Comments