How-tos

IBM Containers: Availability Zones

Share this post:

As of May 23rd IBM Bluemix Container Service now provides a native Kubernetes operations experience while removing the burden of maintaining master nodes. Kubernetes itself is based on the Docker engine for managing software images and instantiating containers. Get the details.

IBM Containers offers a great way to quickly improve the availability of your app that is running in a container group. Building upon the enhanced availability offered by anti-affinity, container groups can now be run across multiple availability zones in the US-South and London regions.

Why use availability zones?

Availability zones allow apps to be run and load balanced across multiple cloud environments of the same IBM Containers region. While the availability zones will share the same API and UI front-end, behind the scenes they are set up as separate full instances of the IBM Containers architecture with separate network and power connections. For the US-South region, both availability zones are located in Dallas. The London region offers availability zones in London and Amsterdam.

In much the same way anti-affinity provides protection from a single physical compute node failure, availability zones protect against a whole cloud failure. By running container groups in two availability zones, your application will remain reachable if one group, or even a whole availability zone becomes completely unreachable. The router will load balance between all available container groups, regardless of which availability zones these groups are running in.

How to use availability zones?

Paid accounts can use multiple availability zones and create highly available containers with global load balancing for their app. Free-trial accounts must upgrade to a paid account to use this feature.

To view the availability zone for your current space, run cf ic info and look for the Availability Zone field. If you want to create containers in a different availability zone, you must run cf create-space <space-name> to create a new space. Once you target the new space, you will use the cf ic reprovision command to provision the space in the new availability zone.
You can also change the availability zone for an existing space, but make sure to back up your containers. Containers and container groups are not migrated to the new availability zone and will be removed during the migration process. Images and volumes are not affected. After your space is reprovisioned, you can start creating your containers in the new availability zone.

For more information about creating highly available container groups across multiple availability zones, see Running highly available container groups in different spaces in the same organization.

More How-tos stories

IBM Cloud Functions: we’re doubling the time limit on executing actions

If you work with Cloud Functions, you know that building serverless applications mainly happens by creating actions–small pieces of code that each do one thing well. You can of course sequence actions together or create event-driven workflows. Through our work with customers, we have realized that some scenarios (for example, image processing, file processing, data pipelines) require more time […]

Continue reading

Plan, create and update deployment environments with IBM Cloud CLI and Terraform

Developers do not like to write the same thing twice. The DRY principle is one example of this. Similarly they don't like having to go through tons of clicks in a user interface to setup an environment. Consequently shell scripts have been long used by system administrators and developers to automate repetitive, error-prone and uninteresting tasks.

Continue reading

Access Groups

IBM Cloud introduces access groups in April 2018 as the platform’s newest feature that makes organizing users and streamlining the assignment of access easier than ever! Previously, IBM Cloud Identity Access and Management (IAM) required access policies to be set for individual users and service IDs. Now with access groups, you can organize users and service IDs into a group and manage access by assigning policies to the group. This will save you time and effort and make your IBM Cloud security efforts more efficient!

Continue reading