What Did We Get?

In this lesson, we will reflect on what we have accomplished so far.

No matter whether you executed jx cluster create or jx install, it was a single command (Cluster Autoscaler in AWS is an exception). With that single command, we accomplished a lot.

  • We created a Kubernetes cluster (unless you executed jx install).
  • We acquired a few Namespaces and a few GitHub repositories.
  • We acquired Ingress (unless it already existed in the cluster).
  • We acquired a bunch of ConfigMaps and Secrets that are essential for what we’re trying to accomplish but will be discussed later.
  • Most importantly, we acquired quite a few applications that are essential for our yet-to-be-discovered goals.

What are those applications? Let’s check it out.

The output is as follows.

As you can see, there are quite a few tools in that Namespace. I won’t dive into them just yet. We’ll become familiar with each as we’re progressing. What matters for now is that we acquired everything we need to manage the full lifecycle of our applications. More importantly, we acquired a process to guide us through that lifecycle. We’ll explore the tools and the process in the follow-up chapters. For now, let’s just say that this is awesome. We acquired a lot (much more than what I shared with you so far) from the execution of a single command.


In the next lesson, we will look at how to release all the resources that we are not using.

Install Jenkins X in an Existing Kubernetes Cluster
What Now?
Mark as Completed
Report an Issue