Controlling the Environments

So far, we’ve seen that Jenkins X created three environments during its installation process.

• We acquired the development environment that runs the tools we need for continuous delivery as well as temporary Pods used during builds.
• We also acquired the staging environment where all the applications are promoted automatically whenever we push a change to the master branch.
• Finally, we have a production environment that is still a mystery.

Does all that mean that we are forced to use those three environments in precisely the way Jenkins X imagined?

The short answer is no. We can create as many environments as we need, we can update the existing one, and we can even delete them. So, let’s start with the creation of a new environment.

Creating an environment