-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add annotation to allow to add custom response headers #9742
Changes from all commits
87f27d9
8c34a2d
15bbdf9
21fc50f
0f5c9fa
d2a2a11
196d49d
ba3525b
3673b36
6836b71
ccb990e
e659988
e82f1cf
42dd6b6
47cb871
0d2ea1a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -209,6 +209,7 @@ The following table shows a configuration option's name, type, and the default v | |
|[syslog-host](#syslog-host)| string | "" || | ||
|[syslog-port](#syslog-port)| int | 514 || | ||
|[no-tls-redirect-locations](#no-tls-redirect-locations)| string | "/.well-known/acme-challenge" || | ||
|[global-allowed-response-headers](#global-allowed-response-headers)|string|""|| | ||
|[global-auth-url](#global-auth-url)| string | "" || | ||
|[global-auth-method](#global-auth-method)| string | "" || | ||
|[global-auth-signin](#global-auth-signin)| string | "" || | ||
|
@@ -1285,6 +1286,10 @@ Sets the port of syslog server. _**default:**_ 514 | |
A comma-separated list of locations on which http requests will never get redirected to their https counterpart. | ||
_**default:**_ "/.well-known/acme-challenge" | ||
|
||
## global-allowed-response-headers | ||
|
||
A comma-separated list of allowed response headers inside the [custom headers annotations](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#custom-headers) | ||
Comment on lines
+1289
to
+1291
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it be possible document how to allow any arbitrary headers (for example for an isolated "dev" environment)? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are several possible solutions to achieve this:
which solution do you like or do you have other ideas? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @rikatz do you have a preference? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I like this. Its behavior is controlled by clear switches. |
||
|
||
## global-auth-url | ||
|
||
A url to an existing service that provides authentication for all the locations. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be made optional?
Many shops will run admission controllers that can achieve the same thing. It would be very inconvenient if we had to force users to now configure allowed headers in two places (admission controller rules and nginx ingress).