Create an AME Kubernetes cluster
Create a new AME Kubernetes cluster
AME Kubernetes clusters can be created through the Avisi Cloud console as well as using the
acloud CLI tool.
The release notes for new AME Kubernetes versions are published at AME Kubernetes - Release notes.
Creating a new cluster
Select the environment
First navigate to the environment in which you wish to create a new cluster. You can find this by navigating to the environments view (console.avisi.cloud/environments) and selecting the environment.
On this page, click the “Create cluster” button on the top right of your screen.
Create cluster page
The create cluster page shows the following information:
- The AME Kubernetes version
- The cloud provider
- The region
- Service Level Agreement for the cluster
- A display name
- Node pools
When you have configured your display name and the node pools, you can press create cluster at the bottom of the page. A background process will start to provision your cluster. This may take up to 10 minutes.
Your control plane should be available within a couple of minutes and can be accessed with
kubectl through the
Download Credentials button on the cluster detail page, or by using
acloud kubeconfig install.
See our How to use kubectl with AME for more information on using
acloud kubeconfig install or
Multi availability zones: Enable support for multiple availability zones. Note that enabling multi availability zones might impact costs, for example when used in conjunction with NAT-gateway. This can not be changed after cluster creation.
Network encryption: Enable encryption at the cluster network layer. This configures the Cluster network plugin to use encryption (only supported by Calico). Note that enabling network encryption has a performance impact.
Private Cluster: Disable the external IP address for nodes within this cluster if supported by the cloud provider (AWS only). This enables a NAT gateway and routes all internet traffic through this gateway, providing nodes with a static outbound IP address. Nodes within the cluster will not receive an external IP.
IP whitelist: Restrict access to the Kubernetes API. See also How To Restrict Kubernetes API server access by IP address
- The creation of a control plane takes around 2 minutes on average.
- Enabling a private cluster will increase the time it takes to provision the cluster due to additional cloud resources being provisioned.
- The creation of nodes in your cluster can take anywhere between a minute to 5 minutes, depending on the cloud provider used.
- AME will automatically retry on failed upgrades. A full cluster creation is usually finished within 7 minutes.