[Announce] API Operator for Kubernetes 1.1.0 Released!

[Pubudu Gunatilaka]

*API Operator for Kubernetes 1.1.0 Released!*

As microservices are increasingly being deployed on Kubernetes, the need to
expose these microservices as well documented, easy to consume, managed
APIs is becoming important to develop great applications. The API operator
for Kubernetes makes APIs a first-class citizen in the Kubernetes
ecosystem. Similar to deploying microservices, you can now use this
operator to deploy APIs for individual microservices or compose several
microservices into individual APIs. With this users will be able to expose
their microservice as managed API in Kubernetes environment without any
additional work.

*Distribution & Documentation*

The distribution of the API Operator can be found in API Operator v1.1.0
GitHub release
<https://github.com/wso2/k8s-api-operator/releases/tag/v1.1.0>.

- Quick Start Guide
<https://github.com/wso2/k8s-api-operator/tree/v1.1.0#quick-start-guide>

- Documentation
<https://github.com/wso2/k8s-api-operator/tree/v1.1.0/docs#api-operator-docs>

*New Features and Improvements*

   1. Support in deploying API operator in multiple docker registries such
   as Docker hub, Amazon ECR, Google container registry, Quay.io and HTTP(S)
   docker registries.
   2. Support in exposing multiple Swagger definitions as an API
   3. Java interceptor support for mediations when exposing APIs.
   4. APIs can be exposed via the Ingress controller or as a Route in
   Openshift.
   5. Serverless(KNative) applications can deploy and manage via the API
   Operator.
   6. Support in applying API management to the microservices that deployed
   in Istio, service mesh.
   7. Support API to handle target endpoints in different namespaces.
   8. Horizontal pod autoscaling support for the target endpoint
   9. Kaniko argument support for Kaniko jobs
   10. CPU and memory allocations for target endpoints


*Bug Fixes*
Fixed Issues
<https://github.com/wso2/K8s-api-operator/issues?q=label%3A1.1.0+is%3Aclosed>

*Known Issues*
All the open issues pertaining to API Operator for Kubernetes 1.1.0 are
reported at GitHub <https://github.com/wso2/k8s-api-operator/issues>.

*How You Can Contribute*

*Mailing Lists*

Join our mailing list and correspond with the developers directly.

   - Developer List: dev at wso2.org | Subscribe <dev-request at wso2.org> | Mail
   Archive <http://mail.wso2.org/mailarchive/dev/>
   - User List: user at wso2.org | Subscribe
<architecture-request at wso2.org> | Mail
   Archive <http://mail.wso2.org/mailarchive/architecture/>

*User Forum*: StackOverflow
<https://stackoverflow.com/questions/tagged/wso2-am>
*WSO2 API Manager Slack Channel:* Join Us on Slack
<https://apim-slack.wso2.com>

*Reporting Issues*

We encourage you to report issues, documentation faults, and feature
requests regarding API Operator for Kubernetes through the GitHub repository
<https://github.com/wso2/k8s-api-operator/issues>.

*Important:* Please be advised that the *security issues *must be reported
to security at wso2.com, not as GitHub issues,  in order to reach the proper
audience. We strongly advise following the WSO2  Security Vulnerability
Reporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting security issues.

*-- The WSO2 API Manager Team --*
-- 
*Pubudu Gunatilaka* | Technical Lead | WSO2 Inc.
(m) +94774078049 | (w) +94112145345 | (e) pubudug at wso2.com
<http://wso2.com/signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/announce/attachments/20200407/b63a29e3/attachment.html>