Container Orchestrators (beta)

What is a Container Orchestrator?

A container orchestrator is a connection to a system that is capable of installing and coordinating containers. CloudBolt supports one container orchestrator currently: Kubernetes. If you are interested in support for other container orchestrators or have other needs for managing containers, please contact us at support@cloudbolt.io.

Creating New Container Orchestrators

CloudBolt Admins can create new container orchestrators by:

  1. Click Admin
  2. Click Container Orchestrators.
  3. Click Add a container orchestrator.
  4. Choose a technology
  5. Provide the details CloudBolt needs to connect to your technology
  6. Click Create
  7. After this, one can add containers to Blueprints in CloudBolt to deploy new Kubernetes resources when users request a service.

Adding Containers to a Blueprint

Kubernetes resources are deployed from a YAML-formatted specification known as a config file. CloudBolt can automatically generate this config file from parameters you define, or you can provide your own file via upload or a remote URL.

Auto-generated config files are currently limited to the Pod resource type and a few parameters. For other resource types, please see examples in the Kubernetes documentation for how to create a config file.

When you provide your own config file, you can templatize it using file inputs. CloudBolt will automatically scan the file contents for template style variables like {{ variable }} and will automatically create file inputs for each variable it discovers. Then, an admin can set default values for those file inputs when editing the Blueprint item where the config file is used. When a user goes to order the blueprint containing the Kubernetes resource, that default value will be used unless they enter a different value on the order form. Before actually using the config file to deploy the Kubernetes resource, CloudBolt will substitute the given values into it and use the result as the specification.

Container Deletion

When you delete a service, CloudBolt will also delete any container resources that were associated with that service. CloudBolt will also make an effort to delete any sub-resources, such as Kubernetes Pods created as part of a Deployment. However, there may be some resource types where sub-resources can’t be detected. If you encounter this, please contact us at support@cloudbolt.io.