pingcap
Allow tidb initializer to run on hostnetwork
Feature Request
Is your feature request related to a problem? Please describe:
On EKS, when pod ENI is enabled, the number of pods with trunk ENI that can be created on each machine is bounded by the number of trunk ENI that can be attached to that instance type. We ran out of ENI on instances that hosts TiDB initializer pod and cluster creation stuck.
Describe the feature you'd like:
We would like a mechanism to allow TiDB initializer pod to run on host network which doesn't require the allocation of a pod ENI.
Describe alternatives you've considered:
Schedule tidb pod to instance group that doesn't support support trunk ENI (t family), but that would make the scheduling of initializer inflexible.
Teachability, Documentation, Adoption, Migration Strategy:
How about adding
HostNetwork *boolas we added for other components?
That would be great!