[RFE] Implement Generic API Batching System

[pfeifferj]

Description

The IBM provider lacks the sophisticated batching system found in the AWS provider, leading to potential API rate limiting and inefficient cloud operations.

Current State: Individual API calls for each operation
Recommended Solution:

• Implement generic batcher pattern similar to AWS provider's Batcher[T input, U output]
• Target VPC instance creation, pricing queries, and load balancer updates
• Include configurable batching windows (idle timeout, max timeout, max items)
• Add request hashing for intelligent grouping by zone/resource group

Benefits:

• Reduced IBM Cloud API rate limiting
• Improved provisioning throughput
• Better resource utilization
• Enhanced observability through batch metrics

we need to research if the IBM cloud API would support this pattern

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pfeifferj]

/remove-lifecycle stale