Step 2: Resources
Configure CPU and memory allocation for your container with intelligent presets and real-time usage monitoring.
Quick Presets
Choose a preset based on your workload type:
Development/Testing
- CPU: 250m (0.25 cores)
- Memory: 256Mi
- Use Case: Minimal resources for testing and development
- Cluster Usage: 12.5% CPU, 6.3% memory
Small Web App
- CPU: 500m (0.5 cores)
- Memory: 512Mi
- Use Case: Light web applications and APIs
- Best For: Simple websites, microservices
Medium Application
- CPU: 1000m (1 core)
- Memory: 1Gi
- Use Case: Standard production workloads
- Best For: Most web applications, API servers
High Performance
- CPU: 2000m (2 cores)
- Memory: 4Gi
- Use Case: Resource-intensive applications
- Best For: Data processing, heavy computation
Custom Configuration
CPU Configuration
- CPU Limit: Set in millicores (500m = 0.5 CPU cores)
- Usage Indicator: Shows percentage of cluster capacity
- Recommendation: Start conservative and scale up based on monitoring
Memory Configuration
- Memory Limit: Set in Mi (Mebibytes) or Gi (Gibibytes)
- Conversion: 1Gi = 1024Mi
- Usage Indicator: Shows percentage of cluster capacity
- Recommendation: Allow 20-30% overhead for your application
Resource Summary
The Current Allocation section displays:
- CPU Allocation: Your selected CPU limit
- Memory Allocation: Your selected memory limit
- Cluster Impact: Real-time view of resource consumption
Understanding Resource Units
CPU Units
- Millicores (m): 1000m = 1 CPU core
- Examples:
- 100m = 0.1 cores (10% of one core)
- 500m = 0.5 cores (50% of one core)
- 1500m = 1.5 cores (1.5 full cores)
Memory Units
- Mebibytes (Mi): Binary measurement (1Mi = 1,048,576 bytes)
- Gibibytes (Gi): 1Gi = 1024Mi
- Examples:
- 128Mi = 134MB
- 512Mi = 537MB
- 1Gi = 1.07GB
- 4Gi = 4.29GB
Resource Planning Guidelines
Application Sizing
- Static Websites: 100m CPU, 128-256Mi memory
- API Services: 200-500m CPU, 256-512Mi memory
- Web Applications: 500m-1 CPU, 512Mi-1Gi memory
- Microservices: 100-300m CPU, 256-512Mi memory
- Background Jobs: 200-500m CPU, 512Mi-2Gi memory
- Databases: 1-2 CPU, 2-8Gi memory
Monitoring and Optimization
- Use the "Low Usage" indicators to optimize resource allocation
- Monitor actual usage after deployment through the metrics dashboard
- Scale resources based on performance patterns
- Consider peak vs average usage when setting limits
Best Practices
Resource Allocation
- Start Conservative: Begin with lower allocations and scale up
- Monitor Usage: Use platform metrics to optimize over time
- Plan for Peaks: Consider traffic spikes and processing bursts
- Cluster Capacity: Be mindful of total cluster resource availability
Performance Optimization
- CPU-bound Applications: Prioritize CPU allocation
- Memory-intensive Applications: Focus on memory limits
- I/O-heavy Applications: Balance CPU and memory appropriately
- Microservices: Use smaller, focused resource allocations
Cost Optimization
- Right-sizing: Avoid over-provisioning resources
- Utilization Monitoring: Regular review of actual vs allocated resources
- Scaling Strategies: Consider horizontal vs vertical scaling
- Development vs Production: Use different resource profiles per environment
Next: Proceed to Step 3 to configure network ports and access settings.