The 21.31 introduced a new opportunity to regenerate your personal API key you use to authenticate your calls with the platform REST API.
You have two options, either using a new Generate new API Key button in
your profile page or using a
HTTP POST to the new API endpoint /v2/users/me/generate-api-key. In both cases
the platform will generate a new API Key and store it in the Database
Please Note Generating a new API key will replace the existing API key. If a new API key is generated, then API calls made with the old API key will fail.
We introduce two-factor (2FA) login authentication to provide an additional layer of security. We use Google Authenticator for the 2FA. If the feature is enabled in the tenant then you can enable it for your account following the instructions in the profile page.
With the platform 21.31 version we introduce a new feature called Component Whitelisting. In verbatim this means we can enable or disable certain integration components in each contract based on the list of components - the Component Whitelist. If the component whitelist is enabled in the tenant the following rules would apply in each contract:
team access level would still be available in your production workspaces.With platform 21.31 we added support for deleting pending invitations to contracts using UI and API.
Now you can delete the user invitation by visiting Members section of the Contract Settings, scrolling down to find the list of Pending Members and clicking to delete. Check the following documentation page for more details.
You can also delete the invitation using the API call.
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 21.31 release we remove Kubernetes namespace hard-coding from our charts to integrate the platform into more Enterprise friendly infrastructures.
IMPORTANT To deploy the platform version 21.31 on top of your existing cluster you would need to re-create the entire kubernetes cluster. We recommend to announce maintenance run since the platform would be down for 10-15 minutes.
Here are the steps necessary for a successful platform deployment:
name and labels.name should be equal to values provided in the values.global.namespaces of HELM3 charts):
apiVersion: v1
kind: Namespace
metadata:
labels:
name: <monitoring_namespace_name_from_values>
name: <monitoring_namespace_name_from_values>
---
apiVersion: v1
kind: Namespace
metadata:
labels:
name: <platform_namespace_name_from_values>
name: <platform_namespace_name_from_values>
---
apiVersion: v1
kind: Namespace
metadata:
labels:
name: <tasks_namespace_name_from_values>
name: <tasks_namespace_name_from_values>
The labels are important to platform’s network functionality.
Platform version 21.31 includes the support of the AWS Network Load
Balancer for ingress LoadBalancer. Here are the details of this change:
aws-efs-csi-driver. This means the AWS EFS storage type is supported in case when Amazon EFS CSI driver is installed on the EKS cluster. You can see more details in the Amazon EFS CSI driver configuration documentation. Here is an example configuration for your guidance:
storage:
slugsSubPath: “slugs”
stewardSubPath: “steward”
storageClassName: “platform-storage-slugs”
persistentVolumeClaimName: “platform-storage-slugs-volume-claim”
type: “aws-efs-csi-driver”
config:
name: “platform-storage-slugs-volume”
path: “/pss”
size: “20Gi”
gid: 1502
fileSystemId: fs-03f24358 # AWS EFS file system ID
global.cloudProvider: AWS in your configuration to enable this (HELM3 values).global.services.dockerRegistry.secured: true
global.services.dockerRegistry.tlsSecretName: "docker-registry-tls"
global.services.certificates.dockerRegistry.name: "docker-registry-tls"
global.services.certificates.dockerRegistry.key: "<<base64 encoded key>>"
global.services.certificates.dockerRegistry.crt: "<<base64 encoded certificate>>"
Please Note:
global.services.dockerRegistry.loadBalancerIp,For 2FA we use Google Authenticator mechanism. To enable the 2FA on the tenant you must perform the following steps:
USER_TOTP_CRYPTO_PASSWORD in the platform secrets part of the HELM3 charts. You must generate it in advance (like pwgen -s 32 -n 1 -B). If this value is not set all the following steps will fail.attributes.feature_flags.enabled_totp to true using a PATCH to /v2/tenants/{TENANT_ID} record (admin access).POST to a new API endpoint /v2/users/:id/disable-totp to clear 2FA setup and enable user to login again using only username and password (admin access).With this release we added HTTPS for external docker registry URI.
News in this section are for our customers who use OEM version of the elastic.io platform.
To facilitate installation of ClickHouse and the required dependencies to run in the High Availability mode we added the following documentation pages:
The newly introduced Component Whitelisting feature
includes changes and parameters only accessible to the tenant administration. Before
you can use the component whitelisting you must enable a dedicated tenant level
parameter (switch) attributes.feature_flags.contract_component_whitelist. Set
it to true using a PATCH to /v2/tenants/{TENANT_ID} record (admin access).
When the tenant level switch is enabled, the system will start the migration and add IDs of all contracts to the components records in cases when the component is used in integration flows of production workspaces. Any subsequent new contracts would only have access to all components in the developer workspaces.
With this release we investigated and implemented integration flow complete network isolation. The traffic is now restricted to/from step pods. Only allowed connection to services required for the runtime.
Invalid '0' value in the required fields with type 'number'.1.2.1Re-assembled message action (maester-client library 3.3.0)3.0.0We released a new version of the component which is not backwards compatible. Users are encouraged to investigate the CSV component documentation to learn about the new component.
The component will not be deployed on top of the old component repository, you can
keep using the old component. At some stage we will deprecate the old one. The new
component is available as csv-v3 component in your components list.
Read CSV attachmentCreate CSV From Message StreamCreate CSV From JSON ArrayRead CSV attachment triggerWrite CSV attachmentWrite CSV attachment from JSON ArrayWrite CSV attachment from JSON ObjectRead CSV file from URL1.0.12.6.263.0.02.0.13.3.01.7.31.0.0We introduce new component for working with platform native object storage called Maester.
Delete ObjectLookup Object (at most one)Lookup ObjectsUpsert Object1.3.0Delay2.6.26 and build type to docker