9 From Conception to Production

 

This chapter covers

  • Building containers with Cloud Native Buildpacks
  • Progressive rollout using general CI/CD tools
  • Logging, metrics, and traces

What I’ve spoken about so far is Knative-as-Knative. But software doesn’t exist in a vacuum—it has to be made and run. To wrap up the book, I’d like to touch lightly on the basics of what comes next in the real, day-to-day work we have to do. Pivotal Tracker calls these “Chores”: things you need to do to make things tidier around the place, so that you can move faster in the future.

We tend to neglect these as a profession. In the kitchens of Michelin-starred restaurants, perfectionist chefs are taught to obsess over mise en place—“Everything in its place.” Before cooking a dish, they want every knife, every herb, every surface, every ingredient, every utensil, every pan, every gas burner, everything, to be clean and sharp and fresh and in the same place as it always is.

Right now you have your software, on to which I imagine you have lavished all the attention and love that you can muster. And you’ve now learned about Knative, which is a system that can launch, run, scale, and wire together your software.

9.1 Turning your software into something runnable

9.1.1 Always use digests

9.1.2 Using Cloud Native Buildpacks (CNBs) and the pack tool

9.2 Getting your software to somewhere it runs

9.3 Knowing how your software is running

9.3.1 Logs

9.3.2 Metrics

9.3.3 Traces

Summary

References