Scenario - Support Kubeflow deployment with an ILB
Open
backlog
- Dominant language
- Just
- Stars
- 33
- Forks
- 35
- Avg merge
- 6d 22h
- Merged PRs (30d)
- 4
Description
The current ingress deploys a public load balancer and there should be a provision to deploy an internal load balancer if required.
Contributor guide
Research direction
Start by reviewing the current ingress deployment configuration and how AKS load balancers are selected. Confirm the desired internal load balancer option and its completion criteria with maintainers; done means deployments can choose an internal load balancer while existing public behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100