-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The docs reference this example with custom headers:
mcpServers:
- name: mcp-server-1 2
streamableHTTP:
url: http://localhost:8080/mcp 3
timeout: 30
sseReadTimeout: 10
headers:
- Authorization: Bearer <token>
- Content-Type: application/json
- Accept: application/json
enableSSE: true
The issue is that in the latest OLS version headers are expected as objects rather than array, and header values must come from secrets.
Version-Release number of selected component (if applicable):
lightspeed-operator.v1.0.7
How reproducible:
Always
Steps to Reproduce:
1. Try to add headers as the doc suggests, API will refuse to add them because it expects map of strings rather than array.
2. If you add them as a map of strings but you simply put a value after the key: controller will complain about not finding the secret.
Actual results:
Docs are outdated
Expected results:
Docs are updated and working examples are provided
Additional info: