What Now?

This was a very short chapter, wasn’t it? There is not much more to learn about manual promotions. All we have to do is execute a single command.

Keep in mind that there are many other things we could do to improve deployment to production. We could add HorizontalPodAutoscaler that will scale the application depending on memory and CPU consumption or based on custom metrics. We could also add additional tests beyond those we added in the Applying GitOps Principles chapter. We won’t work on any of the many improvements we could do since I assume that you already know how to enhance your Helm charts and how to write tests and add their execution to jenkins-x.yaml. What matters is that the process works and it is up to you to change and enhance it to suit your specific needs.

We’ll conclude that we explored the whole lifecycle of an application and that our latest release is running in production.

How to free up the resources?

Now you need to decide whether to continue using the cluster or to destroy it. If you choose to destroy it or to uninstall Jenkins X, you’ll find the instructions at the bottom of the Gist you chose at the beginning of this chapter.

If you destroyed the cluster or you uninstalled Jenkins X, please remove the repositories and the local files we created. You can use the commands that follow for that.

⚠️ Please replace [...] with your GitHub user before executing the commands that follow.