ronnybremer commented on issue #2685:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2685#issuecomment-3681233130
Thank you folks for jumping in on that. Indeed, with the provided
documentation I was able to deploy a correctly configured GatewayProxy with
this config:
```yaml
...
ingress-controller:
...
gatewayProxy:
createDefault: true
provider:
controlPlane:
service:
ipFamilyPolicy: RequireDualStack
plugins:
- name: prometheus
enabled: true
config:
prefer_name: true
- name: real-ip
enabled: true
config:
source: http_x_forwarded_for
trusted_address:
- x.x.x.x/24
- 2001:xxx:xxx:xxx::/64
- name: response-rewrite
enabled: true
config:
headers:
set:
X-Content-Type-Options: nosniff
remove:
- Server
- X-Powered-By
pluginMetadata:
opentelemetry:
collector:
address: jaeger-collector.monitoring:4318
resource:
service.name: APISIX-INGRESS
service.version: 3.14.1
set_ngx_var: true
```
It works perfectly and the warning from my original post is gone.
With the huge amount of changes in the helm specs and the ingress controller
+ apisix it is easy to follow the wrong path of documentation and samples.
Thank you for your assistance.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
