pingcap / pingcap/tidb-operator
Allow tidb initializer to run on hostnetwork
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
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:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue, so first inspect the TiDB initializer pod configuration and its Kubernetes reconciliation path. Determine how host networking should be exposed and applied, then verify that initializer scheduling works without allocating a pod ENI while preserving existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100