When updating the PROXY_CONFIGS_ENDPOINT in the secret system-master-apicast from:
http://<token>@system-master:3000/master/api/proxy/configs
to
http://<token>@system-master.<namespace>.svc.cluster.local:3000/master/api/proxy/configs
The configuration can't be fetched because of this change.
2021/07/28 13:54:35 [debug] 19#19: *140 remote_v2.lua:326: services(): services get status: 301 url: http://<token>@system-master.<namespace>.svc.cluster.local:3000/master/api/proxy/configs/admin/api/services.json, requestID=123456 2021/07/28 13:54:35 [warn] 19#19: *140 remote_v2.lua:250: call(): failed to get list of services: invalid status: 301 url: http://system-master.<namespace>.svc.cluster.local:3000/master/api/proxy/configs/admin/api/services.json, requestID=123456, client: xx.xxx.x.x, server: _, request: "GET /test HTTP/1.1", host: "example.com:443"
The request is to allow using the service hostname system-master-<namespace>.svc.cluster.local by updating the regex in settings.yml to improve the dns query with the following:
apicast_internal_host_regexp: '\Asystem-((master|developer|provider))\Z|(\Asystem-(.*)(.svc.cluster.local\Z))'
- relates to
-
THREESCALE-10218 Allow internal service name in PROXY_CONFIGS_ENDPOINT and BACKEND_ENDPOINT_OVERRIDE
-
- Defined
-
- links to