Planning

The following should be taken into consideration when planning for a TIBCO Cloud™ API Management - Local Edition cluster:

  • How many logical zones make up your API Management - Local Edition cluster?
  • How many Traffic Manager, Cache, NoSQL, and Log service components should each zone have?
  • A minimal Local Edition cluster with one zone and one instance of each component requires 4 CPUs and 16 GB memory.
  • To support high availability (HA) and Resiliency, additional resources (CPU, Memory, and so on) may be necessary.

Since clusters can be set up in many different ways, and can be shared by many applications, it is the Administrator's responsibility to have the cluster set up and be ready for deployment.

For MacOS :

If you have already installed minikube or kubetctl earlier, we suggest reinstalling the software to remove any trace of previous Kubernetes installation

  • rm kubectl
  • rm ~/.kube
  • rm ~/.ssh kube*
  • Export KUBECONFIG=<Path to kubeconfig file>

For the Kubernetes worker nodes, the following k8s_node_size is recommended.

Deployment NODE SIZE
Normal >= 4 vCPU, 16 GB RAM
No OAuth < 4 vCPU, 16 GB RAM

For the Kubernetes master node, the following k8s_master_size is recommended.

Number of Nodes in Cluster NODE SIZE
< 5 < 4 vCPU, 16 GB RAM
6 - 10 4 vCPU, 16 GB RAM
> 10 > 4 vCPU, 16 GB RAM