External Secrets Management
Release can now connect to and access secrets directly from the users AWS or GCP account. Users can seamlessly reference their cloud provider secrets manager (AWS Secrets manager, AWS Parameter Store and GCP Secret Manager) directly from Release without having to copy and paste them into their application templates. This improves security and reduces manual intervention.
Customers can now easily integrate Datadog agents directly into Release. This feature improves the robustness of Release's enterprise offering and provides additional connectivity to 3rd party solutions. Users now have granular control over which clusters they have their datadog agents enabled on.
- Added Identity and Access policies for AWS Shield roles on our load balancers
- Made modifications to improve the reliability of table creation
- Improved the UI experience when creating Instant Datasets
- We now allow account owners to download the kubeconfig file for any of their clusters
- Improved the invitation flow to add users
- We've improved the UI in the admin console for receiving notifications
- Upgraded EC2 versions to support Aurora
- We've made fixes for refreshing a pool of Aurora datasets
Third Party Private Container Registry Support
In addition to allowing users to pull container images from AWS & GCP, we now support obtaining container images in privately stored third party registries. This feature allows customers to connect to one or more private (docker) image registries. These images can then be referenced from the user's app in Release when we run a build. Enabling customers to pull from third party registries expands Release's integration offering in a seamless manner. Learn how to use it on your own here
Usage Based Billing
Release now offers usage based billing, meaning customer's are billed based on the length of time that an environment is running. With a usage based pricing model, customers are only billed based on the value derived from the platform. Release does not limit customers to the number of users nor associates additional fees with user growth, rather lowers the barrier for new customer aquisition and ties together pricing to the value of environment runtime.
- We now uses Chargebee for billing instead of Stripe
- Upgraded Docker Compose to support the latest version of the expose ports API
- Added support for AWS Aurora cloning in Instant datasets to improve performance and reduce storage compared to taking a regular snapshot
- Improved error handling when analyzing projects with Helm charts