Starting from the release 21.35 you can not choose the deprecated components to build your integration flows. The following rules will apply:
While mapping the values the platform UI used to hide the buttons below the input fields for switching between mapping modes (integrator/JSONata) and the mapping preview. You could see these buttons only when you move you mouse over the input fields.
With 21.35 release the mapping modes and previous buttons show permanently.
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.
To support metrics collection in case when the containered runtime is used
(for example AKS) in your cluster, we introduce a new global.containerRuntime
parameter to HELM3 charts (global values.yaml
). It can have two values
docker
(default) or containerd
.
With the platform version 21.35 we added an improved logs and metrics collection
for AKS (Azure Kubernetes Service) based clusters. To enable it set the parameter
global.containerRuntime
to containerd
instead of the default docker
.
In the last release we reported about PSS deprecation. With the current 21.35 we complete the process by making the PSS dependence optional.
.Values.global.services.pss.enabled
as true
in the HELM3 configuration.s3
for the docker registry and the PSS is disabled (the default), the associated pv/pvc
will not be created.With 21.35 we introduce support for Redis Sentinel as en external redis
for the Maester and other internal caching solutions. To use it, ensure related .Values.global.config.*_REDIS_URI
value is not set and the new values for connecting to Sentinel are correctly set.
Here are the newly introduced HELM3 values and their descriptions:
.Values.global.config.CACHE_REDIS_SENTINELS
- Configuration for our caching solution based on Redis. List of sentinels to connect to. Format: array of objects with host
and port
values..Values.global.config.CACHE_REDIS_SENTINEL_NAME
- Configuration for internal caching solution based on Redis. Identifies a group of Redis instances composed of a master and one or more slaves..Values.global.config.CACHE_REDIS_SENTINEL_PASSWORD
- Configuration for internal caching solution based on Redis. Password to authenticate with Sentinel..Values.global.config.MAESTER_REDIS_SENTINELS
- Maester’s Redis configuration. List of sentinels to connect to. Format: array of objects with host
and port
values..Values.global.config.MAESTER_REDIS_SENTINEL_NAME
- Maester’s Redis configuration. Identifies a group of Redis instances composed of a master and one or more slaves..Values.global.config.MAESTER_REDIS_SENTINEL_PASSWORD
- Maester’s Redis configuration. Password to authenticate with Sentinel.News in this section are for our customers who use OEM version of the elastic.io platform.
If the platform services bloody-gate
and knight-of-the-bloody-gate
are
not deployed the agents section, as well as possibility to select Agent while
creating credentials will not show on UI. The platform will not accept
calls to /v2/agents/vpn
API endpoint as well.
No new development were made for components in the release 21.35.