feat: make ingress PathType configurable via Helm env var, default to Prefix #126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
In recent versions of the NGINX Ingress Controller, stricter validation rules have been introduced for
ingress.spec.rules.http.paths.pathwhenpathTypeis set toPrefixorExact. These rules enforce that thepathmust://,_, and-If a path contains characters outside this set (e.g., for rewrite purposes), the
pathTypemust be set toImplementationSpecific. This validation is enforced by the Admission Webhook, and non-compliant ingress resources will be denied admission.To ensure compatibility and prevent potential deployment failures, we are explicitly setting the default
pathTypetoPrefixvia an environment variable in the Helm chart. This default is safe for standard use cases where paths comply with the new restrictions.For advanced use cases involving rewrites or non-standard characters in paths, users should explicitly override the
pathTypetoImplementationSpecific.