The 6.3 release of the Entando platform brings significant new features, bug fixes and architectural updates to speed the development of your micro frontend applications on Kubernetes. The goal of the release is to enhance the platform in three key areas.
The "ent" CLI is a powerful new CLI with 1-line commands to quickly generate, manage, and deploy projects including micro frontends, microservices, pages, and content.
With the release of 6.3 Entando ships with a set of templates to help accelerate the application development process and to provide a set of examples to work from for developers new to Entando.
The Entando App Builder now includes an interactive tutorial to give new developers and users an introduction to creating Entando applications.
When deploying to a Kubernetes cluster the Entando platform now supports configuration under a single domain. In particular, this update will greatly simplify the deployment of the platform on Windows and in cases where local network settings prevent the resolution of DNS services like nip.io or xip.io.
In concert with the ent CLI tool the Entando 6.3 release includes new capabilities to create bundles from running Entando applications. The bundle tool is built to aid in developer workflows to support fast reuse and customization across Entando applications.
The 6.3 release includes a significant expansion of the types of components that can be included in an Entando bundle and deployed via the Entando Component Repository.
The Entando Component Repository provides new features for component lifecycle management that allows developers to force the installation of a component in a given Entando application.
This release includes significant simplification in using private Docker registries for custom image deployment and private GitHub repositories for hosting Entando bundles. In both cases the Entando operator supports the management of Kubernetes secrets to ensure that credentials are stored and accessed securely.
The centralization of the Entando Operator allows operations teams to isolate the operator functionality to manage the lifecycle and operations of many Entando applications in a cluster.
The Entando App Engine supports new high availability and horizontal scaling options with the 6.3 release. The updates are focused on updates to the caching layer including a new implementation using Redis or via Infinispan with JGroups and KUBE_PING.
In many enterprise deployments , customers have an external proxy that will utilize HTTPS that operates independently of K8S and will supersede the TLS functionality provided by K8S ingresses. With this release Entando supports more complex TLS and network topologies including allowing components internal to a cluster to communicate via HTTPS.
With the release of 6.3, Entando now requires Java 11 for all of the Entando base images for enhanced encryption and security. All of the images deployed as part of the 6.3 release have been updated to use OpenJDK Java 11.
The 6.3 release also includes significant changes and updates to the libraries used by the different services in the Entando architecture. As part of our deployment and pipeline process we include vulnerability scanning via Sonar and OWASP detection and numerous libraries have been updated based on those scans.
It's now easier than ever to try Entando. Get your own sandboxed instance on your local machine.