Cloudify Examples: Simple Kubernetes Blueprint

Cloudify Examples: Simple Kubernetes Blueprint

You are here:
< Back

Kubernetes Cluster Example

This blueprint creates an example Kubernetes cluster. It is intended as an example. The underlying Kubernetes configuration method used is Kubeadm, which is not considered production-ready.
Regardless of your infrastructure choice, this blueprint installs and configures on each VM:

    • The Kubernetes Yum repo will be installed on your VMs.
    • Docker, version 1.12.6-28.git1398f24.el7.centos
    • kubelet, version 1.9.3-0.
    • kubeadm, version 1.9.3-0.
    • kubernetes-cni, version 0.6.0-0.
    • weave


You will need a Cloudify Manager running in either AWS, Azure, or Openstack. The Cloudify manager should be setup using the Cloudify environment setup – that’s how we test this blueprint. The following are therefore assumed:

  • You have uploaded all of the required plugins to your manager in order to use this blueprint. (See the imports section of the blueprint.yaml file to check that you are using the correct plugins and their respective versions.)
  • You have created all of the required secrets on your manager in order to use this blueprint. (See #secrets.)
  • A Centos 7.X image. If you are running in AWS or Openstack, your image must support Cloud-init.


Common Secrets:

  • agentkeyprivate
  • agentkeypublic
  • cfy_user
  • cfy_password
  • cfy_tenant

AWS Secrets:

  • vpc_id: This is the ID of the vpc. The same vpc that your manager is attached to.
  • privatesubnetid: This is the ID of a subnet that does not have inbound internet access on the vpc. Outbound internet access is required to download the requirements. It must be on the same vpc designated by VPC_ID.
  • publicsubnetid: This is the ID of a subnet that does have internet access (inbound and outbound). It must be on the same vpc designated by VPC_ID.
  • availabilityzone: The availability zone that you want your instances created in. This must be the same as your publicsubnetid and privatesubnet_id.
  • ec2regionendpoint: The AWS region endpint, such as
  • ec2regionname: The AWS region name, such as ec2regionname.
  • awssecretaccess_key: Your AWS Secret Access Key. See here for more info. This may not be provided as an environment variable. The string must be set as a secret.
  • awsaccesskey_id: Your AWS Access Key ID. See here for more info. This may not be provided as an environment variable. The string must be set as a secret.

Azure Secrets:

  • location: See here.
  • mgrvirtualnetwork_name: This is the name of the virtual network that your manager is attached to.
  • mgrsubnetname: The is the name of the subnet that your manager is attached to.
  • mgrresourcegroup_name: This the resource group that your manager is sitting in.
  • client_secret: Your Azure Service Principal password. See here.
  • client_id: Your Azure Service Principal appId. See here.
  • tenant_id: Your Azure Service Principal tenant. See here.
  • subscription_id: Your Azure subscription ID.

Openstack Secrets:

  • externalnetworkname: This is the network on your Openstack that represents the internet gateway network.
  • publicnetworkname: An openstack network. (Inbound is expected, outbound is required.)
  • publicsubnetname: A subnet on the public network.
  • routername: This is a router that is attached to your Subnets designated in the secrets publicsubnetname and privatesubnet_name.
  • region: Your Keystone V2 region.
  • keystone_url: Your Keystone V2 auth URL.
  • keystonetenantname: Your Keystone V2 tenant name.
  • keystone_password: Your Keystone V2 password.
  • keystone_username:Your Keystone V2 username.

vSphere Secrets:

  • vcenter_user: vCenter/vSphere user name
  • vcenter_password: vCenter/vSphere password name
  • vcenter_ip: vCenter/vSphere host

Step 1: Install the simple Kubernetes cluster

For AWS run:

$ cfy install \ \
-b k8s \
-n aws-blueprint.yaml

For Azure run:

$ cfy install \ \
-b k8s \
-n azure-blueprint.yaml

For Openstack run:

$ cfy install \ \
-b k8s \
-n openstack-blueprint.yaml

You should see something like this when you execute the command:

$ cfy install \ \
-b k8s \
-n aws-blueprint.yaml
Uploading blueprint simple-kubernetes-blueprint/aws-blueprint.yaml...
aws-blueprint.yaml |##################################################| 100.0%
Blueprint uploaded. The blueprint's id is k8s
Creating new deployment from blueprint aws...
Deployment created. The deployment's id is k8s
Executing workflow install on deployment aws [timeout=900 seconds]
Deployment environment creation is in progress...

Step 2: Verify the demo installed and started.

Once the workflow execution is complete, verify that these secrets were created:

(Incubator)UNICORN:Projects trammell$ cfy secrets list
Listing all secrets...
| key | created_at | updated_at | permission | tenant_name | created_by |
| kubernetes-admin_client_certificate_data | 2017-08-09 14:58:06.421 | 2017-08-09 14:58:06.421 | | default_tenant | admin |
| kubernetes-admin_client_key_data | 2017-08-09 14:58:06.513 | 2017-08-09 14:58:06.513 | | default_tenant | admin |
| kubernetes_certificate_authority_data | 2017-08-09 14:58:06.327 | 2017-08-09 14:58:06.327 | | default_tenant | admin |
| kubernetes_master_ip | 2017-08-09 14:56:12.359 | 2017-08-09 14:56:12.359 | | default_tenant | admin |
| kubernetes_master_port | 2017-08-09 14:56:12.452 | 2017-08-09 14:56:12.452 | | default_tenant | admin |

Step 3: Run demo Kubernetes applications

You can now run a demo kubernetes application:

$ cfy install \ \
-b wordpress \
-n examples/wordpress-blueprint.yaml


    Back to top