Fix security headers not being allowed cross-namespace

main
trivernis 1 year ago
parent 06b2b1aefa
commit 9595ebca62
Signed by: Trivernis
GPG Key ID: DFFFCC2C7A02DB45

@ -9,9 +9,9 @@ spec:
routes:
- match: Host(`search.trivernis.dev`) || Host(`search.trivernis.net`)
kind: Rule
middlewares:
- name: strict-security-headers
namespace: default
services:
- name: searxng-srv
port: 8080
middlewares:
- name: strict-security-headers
namespace: default

@ -14,4 +14,4 @@ spec:
customResponseHeaders:
X-Robots-Tag: noindex,nofollow
X-Download-Options: noopen
X-Powered-By: coffee X-Powered-By
X-Powered-By: coffee

@ -15,4 +15,4 @@ spec:
X-Robots-Tag: noindex,nofollow
X-Download-Options: noopen
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: coffee X-Powered-By
X-Powered-By: coffee

@ -8,6 +8,7 @@ spec:
additionalArguments:
- "--entryPoints.web.proxyProtocol.trustedIPs=10.0.0.254"
- "--entryPoints.web.forwardedHeaders.trustedIPs=10.0.0.254"
- "--providers.kubernetescrd.allowCrossNamespace=true"
ports:
web:
exposedPort: 8000

Loading…
Cancel
Save