- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control. - Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities. - Created .gitmodules to include OpenZeppelin contracts as a submodule. - Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment. - Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks. - Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring. - Created scripts for resource import and usage validation across non-US regions. - Added tests for CCIP error handling and integration to ensure robust functionality. - Included various new files and directories for the orchestration portal and deployment scripts.
1021 B
1021 B
HPA Review
Overview
HorizontalPodAutoscaler (HPA) has been configured for RPC nodes to automatically scale based on CPU and memory usage.
HPA Configuration
Target
- StatefulSet: besu-rpc
- Namespace: besu-network
Scaling Parameters
- Min Replicas: 2
- Max Replicas: 10
- CPU Target: 70% utilization
- Memory Target: 80% utilization
Scaling Behavior
- Scale Up: 100% increase or 2 pods per minute (whichever is higher)
- Scale Down: 50% decrease per minute
- Stabilization Window: 300 seconds (scale down), 0 seconds (scale up)
Validation
Run the validation script:
./scripts/validation/validate-hpa.sh
Application
Apply HPA:
kubectl apply -f k8s/base/rpc/hpa.yaml
Testing
Generate load on RPC endpoints and verify HPA scales pods based on CPU/memory usage.
Requirements
- Metrics server must be installed in the cluster
- Resource requests and limits must be set on pods
- HPA requires metrics API to be available