-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
2.11.0 GA
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
Critical
-
Customer Escalated
We are using 3scale 2.11 and Service Mesh 2.1 on OpenShift 4.11.17
I know that strictly speaking 3scale 2.11 is not tested with OCP 4.11 but the issue is not with 3scale directly. Instead it's the WASM module.
When configuring 3scale WASM through ServiceMeshExtensions, WASM fails to start properly.
Configuration and error message shown in attached file extension-status-1.yaml
Documentation still refers to the v0.0.1 image (https://docs.openshift.com/container-platform/4.11/service_mesh/v2x/ossm-threescale-webassembly-module.html)
Steps to reproduce:
- Install OCP 4.11.17 and ServiceMesh 2.1
- Install 3scale on OCP
- Configure ServiceMeshExtensio as described in the attached file
- is triggering
-
THREESCALE-9317 Improve WASM Documentation clarity
- Closed