Defining a Scenario
Define a scenario to implement Helm instructions.
We'll cover the following...
Background
Let’s start with objectives before diving into specific tools. That will help us evaluate whether Helm fits our needs, or if we should look elsewhere. Nevertheless, there is a common theme for almost all of us, and the differences in our situations tend to be smaller than we think. Those differences are often details rather than substantial differentiation.
Most of us are deploying applications to multiple environments. We might have a personal development environment. We might have others for previews generated when creating pull requests and a few permanent environments such as, for example, staging and production. The number might differ from one company to another, and we might label them differently. Nevertheless, we all tend to have more than one environment, with some being dynamic (e.g., personal environments) and others being permanent (e.g., production).
What matters is that applications in different environments tend to have different needs.
On one hand, it would be great if a release in each of the environments was exactly the same. That would give us additional peace of mind, knowing that what we’re testing is exactly the same as what will run in production. That’s the promise of containers. A container based on an image should be the same no matter where it runs. On the other hand, we also want to be pragmatic and cost effective. ...