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
{{ message }}
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
rules that overlap (firt rule wins, event with warning) 766
$ kubectl get ing
NAME RULE BACKEND ADDRESS
demo - 172.17.4.99
foo.bar.com
/ echoheaders-x:80
foo-tls - 172.17.4.99
foo.bar.com
/ echoheaders-x:80
bar.baz.com
/ echoheaders-y:80
NGINX controller e2e tests:
no default backend
invalid default backend
no ingress
single ingress:
rule
invalid service
invalid port
no endpoints
no host (it should use the _ nginx server)
without path
multiple ingress:
rule
invalid service
invalid port
no endpoints
with same path (error or just a warning?)
without path
TLS rules:
invalid certs
invalid hosts (fails verification)
invalid service
invalid port
no endpoints
no host (it should use the _ nginx server)
tcp configmap
invalid service
invalid port
no endpoints
custom nginx configmap
change timeouts
invalid fields
The text was updated successfully, but these errors were encountered:
bprashanth
changed the title
Ideas and missing tests to implement in Ingress controller
Ingress controllers should handle edge cases uniformly x-platform
Apr 13, 2016
Ideas:
—root-url
root-url
. This means the ingress only contains one ruleNGINX controller e2e tests:
The text was updated successfully, but these errors were encountered: