About Minimum System Requirements

The minimum supported network topology for a production environment is a 3-node configuration as shown in the following diagram:

This configuration represents the minimum number of nodes that can enable high-availability and failover. In this configuration, each node hosts the platform applications and services. You must configure a load balancer to use round-robin distribution of traffic among each of the three nodes.

Each node also hosts an instance of the database and file store. Hosting the database and object store enables persistence, but requires larger minimum disk and memory requirements. Although each node contains a database, only one of the database is used as the master. Applications on each node write to this database only. The other two database instances are used for data persistence.

The maximum supported network topology is a 6-node configuration as shown in the following diagram:

In this configuration, three nodes are dedicated to hosting the platform applications and services. You must configure a load balancer to use round-robin distribution of traffic among each of these three nodes.

The other three nodes host the database and file store instances. Although each node contains a database, only one of the database nodes is used as the master. Applications on each node write to this database only. The other two nodes are used for data persistence.

The following Linux distributions are supported:

Anypoint Platform Private Cloud Edition supports the default SELinux profile running in strict mode. If your environment uses a custom profile, it must provide an unconstrained user context when running the installer. Review any custom profiles with your customer support representative.

For production usage, each node in your configuration must meet the following minimum requirements:

Anypoint Platform Private Cloud Edition is only supported on physical servers or VMWare virtualization environments.

In these configurations, to ensure high availability and performance, each node must run on its own physical server. If you are using a virtual machine to host these nodes, you must ensure that each VM node is running on a separate physical server.

All disks should have high performance capability, even if they are virtual block devices or network attached storage.

All disks should have at least 300 MB/sec of throughput.

Each of your disks should meet following performance quotas:

All servers in the cluster should have static private IPv4 assigned to them, these must persist after server restarts. If IP addresses are not persistent between reboots, the cluster may enter a failed state.

The version of Kubernetes supported by Anypoint Platform Private Cloud Edition uses an overlay VXLAN and UDP transport to encapsulate traffic. There is direct communication between components of the cluster via TCP. The table below shows the ports used for inter-host communication. You must ensure that all of these ports are configured correctly.

To run the platform, the IPV4 forwarding flag must be set to true. You must ensure that there are no processes on your system that set this flag to false. If the IPV4 flag is set to false, the platform fails.

In some situation, the Kubernetes overlay network uses NAT. NAT requires that servers be able to send and receive packages with a source and destination that is different from server’s internal IP.

In order to use the Anypoint Platform Private Cloud Edition, you must provide SSL credentials. You can upload a certificate through the Anypoint Platform UI. This certificate must be trusted by every machine that is connected to the platform.

Your network must include an SMTP server to manage e-mail alerts that are triggered by the platform. See Private Cloud Edition Features for information on configuring SMTP for the Anypoint Platform.