We have partnered with many customers that have been using Helm to develop their applications. We have worked with them to combine the simplicity of docker compose based services with the power of Helm. Creating a platform that can orchestrate both of them together.
services:- name: redis:5image: redischarts:- name: elasticsearchadd: elasticrepo_url: https://helm.elastic.codirectory: elasticsearchvalues: values.yaml- name: acme-appdirectory: helmvalues: values.yamlworkflows:- name: setupparallelize:- step: datatasks:- services.redis- charts.elasticsearch- step: acme-apptasks:- charts.acme-app
Visit our documentation on Helm to learn more about how to add open source or your private Helm charts to your applications in Release.
Release now supports authenticating and connecting with Gitlab as a VCS provider. After click the Gitlab button you'll be prompted to authorize Release's OAuth application.
Release currently asks for full permission to Gitlab's API to be able to pull in your code and create builds for your app. We're hoping to work with Gitlab to reduce this requirement to the bare minimum of permissions in the future.
Release is excited to announce GitOps Support! While Release features a simple to use UI for setting up your application and environment configurations some of us live in the command line. In order to use GitOps, contact [email protected] to have us enable it (it’’s beta the moment), then you will want to create a
.releasedirectory in the root of your repository and add two files to it:
environment_variables.yaml. These files can be copied from the App Settings section of your application.
Once you have these files checked into your repository on each push to that branch, Release will look for changes in your configuration and react appropriately. You can have a different version of each file per branch allowing you utmost flexibility while being very simple.
Release now has support for creating multiple Cloud Provider Integrations. The form, shown below allows you to select a provider (currently only Amazon is supported) and input a name for the new integration.
After creating the integration, the information about it is shown. To connect this integration to your AWS account, click the Launch Stack button. After the connection is successful, the Cloud Account ID will be filled in.
Release can now build a new Kubernetes cluster in your AWS Account!