Default Node Groups
Porter provisions three node groups by default:
The application node group autoscales based on demand. You can customize instance types, node counts, and scaling limits for all node groups.
Changing Instance Types
You can modify the instance type for any node group from the Infrastructure settings.1
Navigate to Infrastructure
From your Porter dashboard, click on the Infrastructure tab in the left sidebar.
2
Select your cluster
Click on Overview to view your cluster configuration and node groups.
3
Configure the node group
Expand the node group dropdown (e.g., Default node group) to see the following settings:
4
Update
Select the appropriate Machine type from the dropdown, then scroll to the bottom and click Update.
Instance Type Pricing
AWS Instance Types
Azure Instance Types
GCP Instance Types
Why is my instance type not available?
Instance types may not be available if:- The instance is not available in your cluster’s region (cloud providers release new instances on a phased, region-by-region basis)
- The instance type hasn’t been validated by Porter for compatibility
Creating a Custom Node Group
Create custom node groups for specialized workloads like GPU processing, high-memory applications, or isolated environments.1
Navigate to Infrastructure
From your Porter dashboard, click on the Infrastructure tab in the left sidebar.
2
Select your cluster
Click on Cluster to view your cluster configuration and node groups.
3
Add a node group
Click Add an additional node group to open the configuration panel.
4
Configure the node group
Choose between two configuration approaches:
- Cost Optimization
- Fixed Instance Type
Cost optimization automatically selects the most cost-effective instance types for your workloads. Any cluster provisioned in AWS will default to cost optimized node groups.Set your maximum CPU cores limit to prevent unexpected scaling. This caps infrastructure costs while allowing flexibility in instance selection.
Limitations
The following configurations should use fixed instance types instead:- GPU instances (e.g., instances with NVIDIA GPUs)
- Spot instances
- Instances in public subnets
- Instances with specialized hardware requirements
Health Checks Required: For production applications on cost-optimized node groups, configure proper health checks. This ensures applications can be safely rescheduled as nodes are reshuffled.
5
Save and apply
Click Save to create the node group. Porter provisions the new nodes, which may take a few minutes.
Assigning Workloads to Node Groups
Once your custom node group is created, assign applications to run on it:- Navigate to your application in the Porter dashboard
- Go to the Services tab
- Click the service you want to assign
- Under General, find the Node group selector
- Select your custom node group from the dropdown
- Save and redeploy your application
Deleting a Node Group
To remove a custom node group:- Migrate any workloads running on the node group to another node group
- Navigate to Infrastructure → Cluster
- Find the node group you want to delete
- Click the delete icon and confirm

