Supported Cloud Providers
MetaKube currently supports the following cloud providers and regions for creating Kubernetes clusters:
OpenStack Cloud
Supported regions:
- cbk (Berlin)
- dbl (Berlin)
- fes (Frankfurt)
- dus (Düsseldorf) - see the documentation
- ham (Hamburg) - see the documentation
Note that every region has its own set of resource quotas. You can see the quota for every region in the Horizon Dashboard.
To increase the quota for a region, please contact our Support.
When creating a cluster you have to provide valid OpenStack credentials for the OpenStack tenant that you want to create the cluster in, so that MetaKube can create and manage VMs, Networks, LoadBalancers and Volumes.
For more information see the OpenStack Cloud documentation.
Amazon Web Services
Warning
Deprecated, no new clusters can be created on AWS.
To create clusters with AWS, you need to sign up for AWS separately.
Supported regions:
- EU Frankfurt
- EU Ireland
- EU Stockholm
- EU London
- EU Paris
If you have any questions about the Account or require different regions, please contact our Support.
When creating a cluster you have to provide valid OpenStack Cloud credentials for the OpenStack tenant that you want to get the MetaKube Fee billed to and your AWS IAM information, so that MetaKube can create and manage VMs, Networks, LoadBalancers and Volumes.
Needed IAM permissions
Ensure that the user used to create clusters via MetaKube has (at least) the following IAM permissions:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": "iam:ListInstanceProfiles",
"Resource": "arn:aws:iam::YOUR_ACCOUNT_ID:instance-profile/*"
},
{
"Sid": "VisualEditor1",
"Effect": "Allow",
"Action": [
"iam:GetRole",
"iam:PassRole",
"iam:DetachRolePolicy",
"iam:DeleteRolePolicy",
"iam:ListAttachedRolePolicies",
"iam:ListRolePolicies"
],
"Resource": [
"arn:aws:iam::YOUR_ACCOUNT_ID:role/SpacesMetakube",
"arn:aws:iam::YOUR_ACCOUNT_ID:role/metakube-*"
]
},
{
"Sid": "VisualEditor2",
"Effect": "Allow",
"Action": [
"iam:CreateInstanceProfile",
"iam:DeleteInstanceProfile",
"iam:GetInstanceProfile",
"iam:RemoveRoleFromInstanceProfile",
"iam:DeleteRole",
"iam:AddRoleToInstanceProfile"
],
"Resource": [
"arn:aws:iam::YOUR_ACCOUNT_ID:role/metakube-*",
"arn:aws:iam::YOUR_ACCOUNT_ID:instance-profile/metakube-*"
]
},
{
"Sid": "VisualEditor3",
"Effect": "Allow",
"Action": [
"elasticloadbalancing:ModifyListener",
"sts:GetFederationToken",
"elasticloadbalancing:RegisterTargets",
"elasticloadbalancing:SetIpAddressType",
"elasticloadbalancing:SetRulePriorities",
"elasticloadbalancing:RemoveListenerCertificates",
"elasticloadbalancing:SetWebAcl",
"elasticloadbalancing:CreateListener",
"elasticloadbalancing:DescribeListeners",
"elasticloadbalancing:CreateRule",
"elasticloadbalancing:ModifyTargetGroupAttributes",
"elasticloadbalancing:DeleteRule",
"s3:*",
"elasticloadbalancing:CreateTargetGroup",
"elasticloadbalancing:*",
"elasticloadbalancing:DeregisterTargets",
"elasticloadbalancing:SetSubnets",
"elasticloadbalancing:DeleteTargetGroup",
"elasticloadbalancing:DescribeTargetGroupAttributes",
"elasticloadbalancing:ModifyRule",
"elasticloadbalancing:DescribeTargetHealth",
"elasticloadbalancing:SetSecurityGroups",
"elasticloadbalancing:DescribeTargetGroups",
"ec2:*",
"elasticloadbalancing:DescribeRules",
"elasticloadbalancing:ModifyTargetGroup",
"elasticloadbalancing:DeleteListener"
],
"Resource": "*"
},
{
"Sid": "VisualEditor4",
"Effect": "Allow",
"Action": [
"iam:DeleteInstanceProfile",
"iam:CreateRole",
"iam:DeleteRole",
"iam:AttachRolePolicy",
"iam:PutRolePolicy",
"iam:CreateServiceLinkedRole"
],
"Resource": [
"arn:aws:iam::YOUR_ACCOUNT_ID:role/metakube-*",
"arn:aws:iam::YOUR_ACCOUNT_ID:instance-profile/metakube-*",
"arn:aws:iam::YOUR_ACCOUNT_ID:role/aws-service-role/elasticloadbalancing.amazonaws.com/*"
]
}
]
}
You can find more information on how to create and manage AWS IAM roles and access keys in the AWS documentation.