The DevOps Toolkit Catalogue/

...

/

Deploying the First Release

Deploying the First Release

Let's deploy the first release.

We'll cover the following...

Rolling forward releases manually

Now that we’ve explored the Rollout definition and its associated resources, let’s take a look at the specific customization we’ll need for the first release. The goal is to start simple and progress toward a more complicated outcome later. “Simple,” in this context, means manual approvals for rolling forward releases.

Let’s take a look at the set of values we’ll use to overwrite those set by default in the chart of the demo app that’s stored in the file values-pause-x2.yaml.

Press + to interact
ingress:
  enabled: false
istio:
  enabled: true
hpa: true
rollout:
  enabled: true
  steps:
  - setWeight: 20
  - pause: {}
  - setWeight: 40
  - pause: {}
  - setWeight: 60
  - pause: {duration: 10}
  - setWeight: 80
  - pause: {duration: 10}
  analysis:
    enabled: false

Disabling NGINX Ingress

We can see that ingress.enabled is set to false. Normally, we might not want to have an Ingress definition if we’re using Istio Gateway. However, this app is used for many different examples and isn’t specific to Argo Rollouts, so we’re disabling NGINX Ingress since we won’t need it today.

We have the istio.enabled set to true. The reason should be obvious. We’ll need Istio for the examples that follow. Similarly, we’ll use HorizontalPodAutoscaler, so hpa is set to true as well.

Note: Please go back to the definitions in helm/templates to see how those and other variables are actually used.

Now we’re getting to the important part. We’re enabling the definitions specific to Argo Rollouts by setting the value of rollout.enabled to true.

The role of rollouts.steps

The “real” action is happening through the rollout.steps ...

Ask