dotnet/tye

Ingress should allow picking a specific named binding

Open

#204 opened on Mar 26, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (5,310 stars) (532 forks)batch import
good first issueidea

Description

Today the ingress an pick a service to target but it can't specify which binding on the target service. Today the logic picks the first http binding, then the first https binding but there should be an explicit way to override.

Contributor guide

Tech stack
csharpkubernetes
Domain
infrastructuredevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C# knowledgeUnderstanding of Tye ingress logic
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the C# code in the Tye repository that handles Ingress service binding selection. Identify where the first http and https bindings are chosen. Then propose a new configuration property (e.g., 'bindingName') on the Ingress resource to allow users to specify a specific named binding. Consider adding validation to ensure the named binding exists. Look at existing service binding selection logic and how other configuration properties are implemented.