Creating Node Pools
Node Pools in AWS, GCP, and Azure
As explained in the Creating a Cluster topic, when you're creating a new platform cluster in Amazon Web Services, Google Cloud Platform, or Azure, the default node pool setup that will be used as a starting point for the new cluster is determined by the cluster configuration file created by running apolo admin generate-cluster-config
You can check the default node pool setup in the node_pools section of the cluster.yml
file:
Once the cluster is created and set up by our team, a more detailed information about your cluster's node pools can be viewed by running the apolo admin get-clusters
command in CLI:
If you need to change the your node pools, please contact our team at support@apolo.us
Node Pools in an On-premise Installation
If you prefer to create an on-premise platform cluster, node pools are set up in a more individualized way from the start.
Once the set of machines required for your cluster is agreed upon, all of these machines will be grouped by their operating characteristics. Machines with identical characteristics will be combined into node pools and then given labels based on what node pool they are a part of.
If a need to add a new machine to any of the existing node pools arises, this new machine will have to share the characteristics with other machines of the target node pool. It will also be labeled respectively to make sure it's readable and accessible as a part of this node pool.
Next Steps
Once the node pools are set up, you can start configuring your cluster's usable presets. This will help create an environment streamlined specifically for your development and deployment workflow.
Last updated