A container cloud relies on a container infrastructure that is configured by an administrator outside the CloudCenter platform. Currently CloudCenter supports one container cloud: Kubernetes cloud. The CCO and AMPQ components associated with a container cloud are deployed on separate VMs outside of the container infrastructure.
Kubernetes cloud configurations require:
Kubernetes version support:
A single Kubernetes cluster with an implicit default region
One or more cloud accounts
Cloud settings API endpoint
Instance types (fractional CPU and memory)
To ensure scalabiilty, install the CCO and AMQP components where they are closer in network reachability to the Kubernetes cluster.
See Convert to a Kubernetes-Specific CCO if you prefer to convert an existing CCO to a Kubernetes-specific CCO.
No additional steps are required to use the AMQP appliance for a Kubernetes cloud.
Upstream Support and Capability
CloudCenter supports upstream Kubernetes setups. Upstream refers to any bare Kubernetes setup like Google Kubernetes Engine (GKE), AWS Kubernetes Operations (Kops), Cisco Container Platform, and so forth as these environments exposes the Kubernetes APIs to users. This term does not include platforms that only use Kubernetes and then add on their own APIs.
CloudCenter's API layer handles configuration tasks such as application deployment for Kubernetes pods – at the time of application deployment, the CloudCenter platform dynamically creates the application pod information, which can be in Kubernetes as YAML or JSON files. The CloudCenter platform dynamically deploys applications based on the CloudCenter application profile. While you cannot directly modify the application pod information that is dynamically created, you can edit the CloudCenter application profile in JSON format. See Application Profile Export/Import > JSON Schema for additional details.
When creating an application profile, users define the network service. The CloudCenter platform uses these user-configured network settings to automatically deploy load balancers through Kubernetes. See Container Service > Deploying a Container Service > Network Services for details.
The Firewall Rules in the application profile correspond to a Network Policy Ingress rules in Kubernetes. See Container Service > Deploying a Container Service > Firewall Rules for details.
Not Required or Not Supported for Kubernetes Environments
Kubernetes environments do NOT require:
The Guacamole component
Kubernetes environments do not support:
IPAM and VM naming callout
Logical image mapping in region
Container power on/off/reboot
Override of instance type cost-based on image
Aging and Suspension Policies (including the Policy Settings tab in pure container environments)
- No labels