We would like to inform you all about the impending roll-out of the new Flows page during our next 21.49 release (9th of December 2021). Our OEM customers will receive the detailed explanation of changes in advance.
The platform user interface has gone through changes in the last year. Some pages like the Executions and Logs use the new unified design. We have still some way to go for a complete transition into the new unified look.
Our team has been working hard to transition the Flows page as well. We are ready to show you what is coming during our next release in two weeks:
Picture shows the flow card changes.
Picture shows the flow card menu changes.
The release 21.47 release contains behind the scene improvements to the platform backend, more relevant to our OEM and on-prem customers.
SCRAM-SHA-256 authentication for MongoDB.
We constantly improve different aspects of HELM3 deployments in collaborations with our partners. This section lists updates and improvements done in this round.
During the 21.45 deployment of flow quota feature the sync process was failing the health-check and the Kubernetes was constantly killing it. Our investigation showed that the sync process must be done in batches. For this purpose we introduce the following new parameters.
QUOTA_SYNC_BATCH_SIZE is equals 20 by default
MAX_BATCH_SIZE environment variable (50 by default)
Values.secrets.platform.config.QUOTA_MAX_BATCH_SIZE - Optional. Use to override default value of maximum batch size limit in the
Values.secrets.platform.config.API_QUOTA_SYNC_BATCH_SIZE - Optional. Use to override default value of batch size for the Quota synchronisation.
News in this section are for our customers who use OEM version of the elastic.io platform.
With 21.47 we introduce a possibility to configure custom login and
logout redirect URL for our OEM customers. You can use this with
providers to streamline and unify customer management in your entire ecosystem.
To setup redirects you need to update (
PATCH) your tenant record and add the required
parameters following this example:
Our API documentation contains the instruction on how to update tenant record.
Along with this addition we introduce a new API endpoint for deleting the OIDC provider record: