Releases: wso2/apk
WSO2 API Platform For Kubernetes 0.0.1-M4 Released
Product releases come as a helm chart that you can install in your kubernetes cluster. We have already tagged and released necessary docker images to the docker registry. Helm install will download necessary components and install them in the k8s cluster.
Refer here for getting started.
What's New On WSO2 API Platform For Kubernetes Milestone 4
Runtime API
- Https API support.
BackOffice API
- API Search support.
Devportal API
- Filter APIs based on API Status.
Adapter
- Support Response header modifications.
- Support resource level endpoints.
- Backend policy support.
Enforcer
- Add keyType claim validation for token validation.
Management Server
- Add gRPC notification server for internal domain services.
Non-Production IDP
- DCRM support.
- Token Generation support.
- Authorization_code support.
Common
- Enable authentication for domain service apis through GW.
We have following known limitations in the WSO2 API Platform For Kubernetes 0.0.1-M4 release
-
Initial version does not support organization management, user management or permission control.
-
This version does not support key management integrations or IDP integration.
Fixed Issues
See details of all the changes including features, improvements, and bug fixes
Known Issues
All the open issues pertaining to WSO2 API Platform For Kubernetes 0.0.1-M4 are reported here.
How To Contribute
Your feedback is most welcome!
Community
You can use our Discord Channel and Stackoverflow Collective to engage with a wider audience https://wso2.com/community/
Reporting Issues
We encourage you to report issues, improvements, and feature requests regarding WSO2 API Manager through WSO2 APK GIT Issues.
And please be advised that security issues must be reported to [email protected], not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.
~ WSO2 API Platform For Kubernetes Team ~
WSO2 API Platform For Kubernetes 0.0.1-M3 Released
Product releases come as a helm chart that you can install in your kubernetes cluster. We have already tagged and released necessary docker images to the docker registry. Helm install will download necessary components and install them in the k8s cluster.
Refer here for getting started.
What's New On WSO2 API Platform For Kubernetes Milestone 3
Runtime API
- Export Runtime API.
- Create new API Version.
- Ability to invoke APIs created with external backend.
BackOffice API
- API category support.
- Merge internal back office DS.
Devportal API
- Retrieve supported SDKs per API through API response.
- API content search capability.
Adapter
- Ability to enable/disable management server connection.
- API context validation across all namespaces.
- Escape regex meta characters in path when type is Exact or PathPrefix.
- Support external service proxying.
Enforcer
- Disable JWT subscription validation for system APIs.
Management Server
- Configure TLS for management server and adapter communications.
We have following known limitations in the WSO2 API Platform For Kubernetes 0.0.1-M3 release
-
Product APIs do not support any security by default. To protect APIs users need to font them with proxy or gateway.
-
Initial version does not support organization management, user management or permission control.
-
This version does not support key management integrations or IDP integration.
Fixed Issues
See details of all the changes including features, improvements, and bug fixes
Known Issues
All the open issues pertaining to WSO2 API Platform For Kubernetes 0.0.1-M3 are reported here.
How To Contribute
Your feedback is most welcome!
Community
You can use our Discord Channel and Stackoverflow Collective to engage with a wider audience https://wso2.com/community/
Reporting Issues
We encourage you to report issues, improvements, and feature requests regarding WSO2 API Manager through WSO2 APK GIT Issues.
And please be advised that security issues must be reported to [email protected], not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.
~ WSO2 API Platform For Kubernetes Team ~
WSO2 API Platform For Kubernetes 0.0.1-M2 Released
Product releases come as a helm chart that you can install in your kubernetes cluster. We have already tagged and released necessary docker images to the docker registry. Helm install will download necessary components and install them in the k8s cluster.
Refer here for getting started.
What's New On WSO2 API Platform For Kubernetes Milestone 2
Runtime API
- API Context,Name Availability API.
- Ability to add un-authenticate resources.
BackOffice API
- Retrieve/Block/Unblock Subscriptions
- API retrieval flow
- API definition retrieval flow
- API update flow
Admin API
- Adding API Categories
Devportal API
- API SDK generation and Download.
- API Definition retrieval flow.
Adapter
- Add header request intercepting
- Support Authentication updates
We have following known limitations in the WSO2 API Platform For Kubernetes 0.0.1-M2 release
-
Product APIs do not support any security by default. To protect APIs users need to font them with proxy or gateway.
-
Initial version does not support organization management, user management or permission control.
-
This version does not support key management integrations or IDP integration.
Fixed Issues
See details of all the changes including features, improvements, and bug fixes
Known Issues
All the open issues pertaining to WSO2 API Platform For Kubernetes 0.0.1-M2 are reported here.
How To Contribute
Your feedback is most welcome!
Community
You can use our Discord Channel and Stackoverflow Collective to engage with a wider audience https://wso2.com/community/
Reporting Issues
We encourage you to report issues, improvements, and feature requests regarding WSO2 API Manager through WSO2 APK GIT Issues.
And please be advised that security issues must be reported to [email protected], not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.
~ WSO2 API Platform For Kubernetes Team ~
WSO2 API Platform For Kubernetes 0.0.1-M1 Released
With this release we would like to Introduce our new cloud native API management platform APK, designed to help you build, deploy, and manage APIs in a cloud environment. Our platform is built on top of a microservices architecture and uses containerisation technologies to ensure scalability and flexibility. With features like automatic failover and load balancing, our APK platform is designed to be highly available and able to handle large numbers of API requests without performance degradation. We've also added support for continuous delivery and deployment, so you can quickly and easily push updates to your API services.
Some characteristics of WSO2 API Platform For Kubernetes
-
Scalability: Designed to scale up and down based on demand, allowing them to handle large numbers of API requests without performance degradation.
-
High availability: Designed to be highly available, with features like automatic failover and load balancing to ensure that API services are always available to clients.
-
Elasticity: Designed to be elastic, meaning that they can quickly and easily adapt to changes in demand and workload.
-
Micro-services architecture: Built using a micro-services architecture, which allows for more flexible and scalable deployment of API services.
-
Containerization: Use containerization technologies to package and deploy product API services/ implementations in a cloud environment.
-
Continuous delivery and deployment: Support continuous delivery and deployment, allowing developers to quickly and easily push updates to API services.
In the initial release of APK we will support limited capabilities and profiles needed to support basic API Management capabilities. In the initial release we will have the following components in our distributions come as docker images.
-
Control Plane - The APK control plane. It provides API Management capabilities, marketplace capabilities along with domain services and web applications. It consists of the following sub-components:
-
Back Office Domain Service - Responsible for configuring the portal aspects of API including descriptions, documents, images, etc. Also, manage API visibility and lifecycle. The backend component was developed using Ballerina.
-
Dev Portal Domain Service - Responsible for API consumer interaction. API consumers can discover APIs, read documents, try them out and eventually subscribe to and consume APIs. The backend component was developed using Ballerina.
-
Admin Portal Domain Service - Responsible for configuring rate limit policies, key management services, and other administrative tasks. Backend components developed using Ballerina.
-
Management Server - Responsible for communication with data planes and pushing updates. Backend components developed using Go lang.
-
-
Data Plane - The APK data plane. It provides API runtime capabilities such as gateway, rate-limiting services, and runtime management. It consists of the following sub-components:
-
Runtime Manager - Responsible for configuring the runtime aspects of API including API endpoints, discovering Kubernetes services, and converting them into APIs, etc. The backend component was developed using Ballerina.
-
Management Client - The management client configures the API gateway’s Router and Enforcer dynamically during the runtime upon receiving an event for API creation or update. It is also responsible for communication with the management server(control plane) to push/pull updates and maintain connectivity between the data plane and the control plane. The component was developed using Go.
-
API Gateway - Router - Router will intercept incoming API traffic and apply quality of services such as authentication, authorization, and rate limiting. The router uses the Envoy Proxy as the core component that does the traffic routing. Required additional extensions were developed using C++
-
API Gateway - Enforcer - The Enforcer is the component that enforces the API management capabilities such as security, Rate Limiting, analytics, validation etc. When the Router receives a request, it forwards that request to the Enforcer in order to perform the additional QoS. Plugins were developed using Java
-
Product releases come as a helm chart that you can install in your kubernetes cluster. We have already tagged and released necessary docker images to the docker registry. Helm install will download necessary components and install them in the k8s cluster.
Refer here for getting started.
WSO2 API Platform For Kubernetes have following capabilities via REST API calls.
Runtime API
- View services in given k8s cluster/namespace
- Check httpbin service is in active state
- View APIs in given k8s cluster/namespace
- Import service and create API, deploy to gateway
- Get API details by ID
- Update API by providing additional details
- Delete API
- Try to get API details by providing already created API ID
- Create another API pointing httpbin service
- Get API details by ID
- Generate test token for created API
- Invoke API using generated test token
BackOffice API
- List all APIs through back office APIs as API product manager
- Change the Lifecycle of the API
- Retrieve current Lifecycle of an API
- Retrieve Lifecycle history of an API
Internal BackOffice
- Create managed API entry from service call
- Update managed API entry from service call
- Update API definition entry from service call
- Delete API from service call
Admin API
- List deny/block policies created in the system
- Create new deny/block policy
- Update created deny policy details and verify change
- Create Application Rate Plan
- View Application Rate Plan
- List all Application Rate Plans
- Update Application Rate Plan
- Delete Application Rate Plan
Devportal API
- Create Application
- View Application
- List all Applications
- Delete Application
- Create Subscriptions
- Create Multiple Subscriptions
- Delete Subscription
- View Subscription
- List all Subscriptions per API or Application
- Create API Key and invoke API using API Key
We have following known limitations in the WSO2 API Platform For Kubernetes 0.0.1-M1 release
-
Product APIs do not support any security by default. To protect APIs users need to font them with proxy or gateway.
-
Initial version does not support organization management, user management or permission control.
-
This version does not support key management integrations or IDP integration.
-
All product interactions need to happen via REST APIs and there won't be any UIs in this release. We have provided Postman collections to try out all operations supported by the product and users can use them to invoke product API.
Fixed Issues
See details of all the changes including features, improvements, and bug fixes
Known Issues
All the open issues pertaining to WSO2 API Platform For Kubernetes 0.0.1-M1 are reported here.
How To Contribute
Your feedback is most welcome!
Community
You can use our Discord Channel and Stackoverflow Collective to engage with a wider audience https://wso2.com/community/
Reporting Issues
We encourage you to report issues, improvements, and feature requests regarding WSO2 API Manager through WSO2 APK GIT Issues.
And please be advised that security issues must be reported to [email protected], not as a GitHub issue, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines when reporting the security issues.
~ WSO2 API Platform For Kubernetes Team ~