ingress-nginx-helm/search/search_index.json

1 line
525 KiB
JSON
Raw Permalink Normal View History

2025-02-03 12:03:43 +00:00
{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Overview","text":"<p>This is the documentation for the Ingress NGINX Controller.</p> <p>It is built around the Kubernetes Ingress resource, using a ConfigMap to store the controller configuration.</p> <p>You can learn more about using Ingress in the official Kubernetes documentation.</p>"},{"location":"#getting-started","title":"Getting Started","text":"<p>See Deployment for a whirlwind tour that will get you started.</p>"},{"location":"e2e-tests/","title":"E2e tests","text":""},{"location":"e2e-tests/#e2e-test-suite-for-ingress-nginx-controller","title":"e2e test suite for Ingress NGINX Controller","text":""},{"location":"e2e-tests/#admission-admission-controller","title":"[Admission] admission controller","text":"<ul> <li>should not allow overlaps of host and paths without canary annotations</li> <li>should allow overlaps of host and paths with canary annotation</li> <li>should block ingress with invalid path</li> <li>should return an error if there is an error validating the ingress definition</li> <li>should return an error if there is an invalid value in some annotation</li> <li>should return an error if there is a forbidden value in some annotation</li> <li>should return an error if there is an invalid path and wrong pathType is set</li> <li>should not return an error if the Ingress V1 definition is valid with Ingress Class</li> <li>should not return an error if the Ingress V1 definition is valid with IngressClass annotation</li> <li>should return an error if the Ingress V1 definition contains invalid annotations</li> <li>should not return an error for an invalid Ingress when it has unknown class</li> </ul>"},{"location":"e2e-tests/#affinity-session-cookie-name","title":"affinity session-cookie-name","text":"<ul> <li>should set sticky cookie SERVERID</li> <li>should change cookie name on ingress definition change</li> <li>should set the path to /something on the generated cookie</li> <li>does not set the path to / on the generated cookie if there's more than one rule referring to the same backend</li> <li>should set cookie with expires</li> <li>should set cookie with domain</li> <li>should not set cookie without domain annotation</li> <li>should work with use-regex annotation and session-cookie-path</li> <li>should warn user when use-regex is true and session-cookie-path is not set</li> <li>should not set affinity across all server locations when using separate ingresses</li> <li>should set sticky cookie without host</li> <li>should work with server-alias annotation</li> <li>should set secure in cookie with provided true annotation on http</li> <li>should not set secure in cookie with provided false annotation on http</li> <li>should set secure in cookie with provided false annotation on https</li> </ul>"},{"location":"e2e-tests/#affinitymode","title":"affinitymode","text":"<ul> <li>Balanced affinity mode should balance</li> <li>Check persistent affinity mode</li> </ul>"},{"location":"e2e-tests/#server-alias","title":"server-alias","text":"<ul> <li>should return status code 200 for host 'foo' and 404 for 'bar'</li> <li>should return status code 200 for host 'foo' and 'bar'</li> <li>should return status code 200 for hosts defined in two ingresses, different path with one alias</li> </ul>"},{"location":"e2e-tests/#app-root","title":"app-root","text":"<ul> <li>should redirect to /foo</li> </ul>"},{"location":"e2e-tests/#auth-","title":"auth-*","text":"<ul> <li>should return status code 200 when no authentication is configured</li> <li>should return status code 503 when authentication is configured with an invalid secret</li> <li>should return status code 401 when authentication is configured but Authorization header is not configured</li> <li>should return status code 401 when authentication is configured and Authorization header is sent with invalid credentials</li> <li>should return status code 401 and cors headers when authentication and cors is configured but Authorization header is not configured</li>