The June 2021 Payara Platform release is here! Payara Enterprise 5.28.1 includes 5 bug fixes and 2 component upgrades along with a community contribution from AngelTG2 for improving loading time for REST applications when there are many password aliases.
In addition to the bug fixes, component upgrades, and community contribution improvement, the Payara Community 5.2021.4 release also introduces a new AutoScale feature in Payara Server to achieve dynamic scalability of instances based on application usage.
Read more below to find out the details.
AutoScale Support for SSH Nodes in Community Edition
Available in Payara Server Community Edition, the new AutoScale feature has laid the groundwork for scaling the deployment of an application to multiple instances automatically based on application resource usage.
In the future, AutoScale will be further developed to integrate with Cloud providers and other frameworks (like Kubernetes) so the Payara environment can scale according to the load of the application.
Watch the blog for an upcoming article about what the current version of AutoScale can do and how to use it, or read more in our Community Documentation.
As announced in the Payara Platform Roadmap 2021, work on logging improvements in Payara Platform has begun. Over the next four to six months, Payara Platform Community and Enterprise releases will include improvements to develop a better logging system.
Payara Kubernetes Operator (Proof of Concept)
The Payara Kubernetes Operator is capable of creating a scalable Deployment Group within Kubernetes that runs an application.
Setting up a Deployment Group within Kubernetes is already possible but it's a non-trivial task that requires a lot of manual work. With the help of the Payara Kubernetes Operator, these can be automated by specifying some properties in a Kubernetes CRD file.
Led by Rudy De Busscher, the Payara Kubernetes Operator is available starting with the June 2021 release as a proof of concept. The operator starts up the DAS, creates the Deployment Group, spins up the number of instances it needs, and deploys your application.
You can build the Payara Kubernetes Operator yourself from code (Proof of Concept Documentation) or you can use it by referring to the Docker Image name in a config file.
In future updates to the Payara Kubernetes Operator, we'll add support for setting environment variables and secrets, support for a web application stored outside of the Application Image, and support for updating the application using the rolling upgrade capabilities of Kubernetes.
The Enterprise Release (request here) includes 5 bug fixes, 1 improvement, and 2 component upgrades; while the Community Release (direct download here) includes 1 new feature, 5 bug fixes, 1 improvement, and 2 component upgrades.
See more detailed overview of the fixes and improvements in the Release Notes:
It's also important to highlight that monitoring data is currently not available on JDK 8u292 and 11.0.11 or later due to the removal of SSL/TLS 1.0 and 1.1 protocols in the latest OpenJDK versions. The Payara team is working on a fix for it.