You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shaun-nx
added
bug
An issue reporting a potential bug
proposal
An issue that proposes a feature request
and removed
bug
An issue reporting a potential bug
labels
Feb 26, 2024
Describe the bug
@btsuhako encountered a bug with the current implementation of the
nginx.org/use-cluster-ip
annotation. It does not currently account for named ports.To Reproduce
examples/ingress-resources/complete-example
changing the field insideport
fromnumber: 80
toname: http
kaf ./examples/ingress-resources/complete-example/
minikube tunnel
curl -k https://cafe.example.com/tea
andcurl -k https://cafe.example.com/coffee
use-cluster-ip
annotation as follows.kaf ./examples/ingress-resources/complete-example/
Expected behavior
NIC handles the two mutually exclusive ways of defining a Port for the
use-cluster-ip
annotation. Number, or NameYour environment
Additional context
Add any other context about the problem here. Any log files you want to share.
The text was updated successfully, but these errors were encountered: