Upgrading Ingress Rules and Adding TLS Certificates

All the applications we installed so far are accessible through a plain HTTP protocol. As I’m sure you’re aware, that is not acceptable. All public-facing applications should be available through HTTPS only, and that means that we need TLS certificates. We could generate them ourselves for each of the applications, but that would be too much work. Instead, we’ll try to figure out how to create and manage the certificates automatically. Fortunately, Jenkins X already solved that and quite a few other Ingress-related challenges. We just need to learn how to tell jx what exactly we need.

All the jx upgrade commands we explored so far have followed the same pattern, they upgrade components to a specific or the latest release. Ingress is the exception. We can use the jx upgrade ingress command to change a variety of things.

• We can change the domain of the cluster or a namespace.
• We can add TLS certificates to all Ingress endpoints.
• We can also change the template Jenkins X is using to auto-generate addresses of applications.

Confirming the deployment

Let’s start by checking the applications we currently have in our cluster.