Chapter 15. Software Supply Chain
Implementing a Kubernetes platform should never be the goal of your team or company (assuming you are not a vendor or consultant!). This might seem a strange claim for a book exclusively devoted to Kubernetes to make, but let’s step back a moment. All companies are in the business of delivering their core-competency. This might be an ecommerce platform, a SaaS monitoring system, or an insurance website. Platforms like Kubernetes (and almost any other tooling) exist to enable the delivery of core business value, a truth that is often forgotten by teams when designing and implementing IT solutions.
With that sentiment in mind, this chapter will focus on the actual process of getting code from developers to production on Kubernetes. To best cover each stage that we think is relevant, we’ll follow the model of a pipeline that many are familiar with.
First we’ll look at some of the considerations when building container images (our deployed assets) from source code. If you’re already utilizing Kubernetes or other container platforms you’ll probably be familiar with some of the concepts in this section, but hopefully we’ll cover some questions that you may not have considered. If you’re new to containers this will be a paradigm shift from the way that you currently build software (WAR files, Go binaries, etc.) to thinking about the container image and the nuances involved with building and maintaining them.
Once we have built our assets we need somewhere ...
Get Production Kubernetes now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
