With the 21.33 platform version we are changing the schedule of release notes to every 2 weeks instead of every 4 weeks to synchronise with the release of HELM3 charts. Our commitment to deliver release to our OEM customers every 4 weeks remains unchanged.
Starting from the 21.33 version you can clearly identify the platform software version in the UI and in the header of every authorised API call response.
Please note This is an optional, configurable setup and your tenant administration might choose not to show this information in your case.
The authorised API call response would contain the platform version in the header
We are in middle of constantly improving various aspects of HELM3 deployments in collaborations with our partners. These are updates and improvements done in this round.
With introduction of platform software version option
we added a new configuration parameter
the HELM3 charts with a default value
true (to show on the UI).
With the deprecation of Platform Storage Slugs service we introduce a parameter which you can used to ensure backward compatibility in cases when you wish to keep the attachments longer in your installation.
A standard procedure is to save the attachment for the period of integration flow
execution process. This is determined with a parameter
which we recommend to set 1 or 2 days. If your system setup has longer periods set
for attachments then you must set the
PSS_BACKWARD_COMPATIBILITY parameter in the
values.yaml of the HELM3 chart to
true so your system can use the old attachments
created before the deployment of 21.33 platform version.
Please Note We recommend keeping the
truefor the period indicated in your
STEWARD_ATTACHMENTS_LIFETIME_DAYSparameter and setting it to
falseafter the indicated period of over.
News in this section are for our customers who use OEM version of the elastic.io platform.
From the platform release 21.33 we are deprecating the Platform Storage Slugs (PSS) service and transferring all attachment and objects storage capabilities to our Maester service. This deprecation would not be felt by the regular users of the platform. All existing endpoints to submit and retrieve attachments will not change. The following change will take affect in the back-end of the platform:
buildType: dockerwill be the only supported build process. We will enforce it even if it is not explicitly set in the
component.jsonof your component. This will prevent saving the components code as slugs (the old method).
Please Note Deprecation of PSS service is applicable/relevant for existing on-prem installations of the platform. All new installations from the version 21.33 are not affected.
With 21.33 release we extended and improved the AKS (Azure k8s) support. In particular:
jsonformats for cases with
Get New and Updated Objects Pollingtrigger:
maxFetch should be maximum 10000 objectsis removed