steveliem
steveliem
In the code I detected a similar commentary like in the ID3 specs: There is the possibility to put only a link to the image file by using the 'MIME...
https://github.com/cosmin/stashy/blob/ae8c08991678c00d63ddb29fa7b26861e444229f/stashy/client.py#L73 In this specific line the code causes a 404 error, resource not found. This is because we have to add the extra 'core_api_path' string behind the '/rest/'. Then we...
**Description:** I am experiencing an issue where APIs deployed in a namespace other than the one where the WSO2 APK dataplane is running do not respond as expected. The setup...
**Description:** Using the WSO2 APK Helm chart (apk-helm-1.0.0), a potential bug related to cross-namespace route acceptance has been observed. The default Gateway configuration, deployed in the `apk` namespace, includes `allowedRoutes.namespaces.from:...
**Description:** Following the installation guideline to provision APK Helm chart. However Helm install fails due to missing values in default "values.yaml". Beginning of January it did work. So I'm assuming...
### Problem I have successfully configured WSO2 API Platform for Kubernetes (APK) on OpenShift, integrating it with Keycloak as the identity provider. This setup allows for API deployment across multiple...
### Description I encountered an issue in the WSO2 API Platform for Kubernetes (APK) where, after deleting a token issuer, previously issued tokens continue to grant access to APIs. This...
### Description I am encountering deployment issues with the WSO2 API Platform for Kubernetes (APK) on OpenShift due to hardcoded `runAsUser` and `runAsGroup` values in the Helm chart, specifically within...