Using Code Examples Every pattern is backed with fully executable examples, which you can find on the accompanying web page. You can find the link to each pattern’s example in the “More Information” section of each chapter. The “More Information” section also contains many links to further information related to the pattern. We keep these lists updated in the example repository. Changes to the link collections will also be posted on Twitter. The source code for all examples in this book is available at GitHub. The repository and the website also have pointers and instructions on how to get a Kubernetes clus‐ ter to try out the examples. When you go through the examples, please also have a look into the provided resource files. They contain many useful comments that help further in understanding the example code. Many examples use a REST service called  random-generator  that returns random numbers when called. It is uniquely crafted for playing well with the examples of this book. Its source can be found at GitHub as well, and its container image  k8spat terns/random-generator  is hosted on Docker Hub. For describing resource fields, we use a JSON path notation. For example,  .spec.rep licas  points to the  replicas  field of the resource’s  spec  section. If you find an issue in the example code or documentation or if you have a question, don’t hesitate to open a ticket in the GitHub issue tracker. We monitor these GitHub issues and are happy to answer any questions over there. All example code is distributed under the Creative Commons Attribution 4.0 (CC BY 4.0) license. The code is free to use, and you are free to share and adapt it for com‐ mercial and noncommercial projects. However, you should give attribution back to this book if you copy or redistribute the material. This attribution can be either a reference to the book including title, author, pub‐ lisher, and ISBN, as in “ Kubernetes Patterns  by Bilgin Ibryam and Roland Huß (O’Reilly). Copyright 2019 Bilgin Ibryam and Roland Huß, 978-1-492-05028-5.” Alternatively, add a link back to the accompanying website along with a copyright notice and link to the license. We love code contributions, too! If you think we can improve our examples, we are happy to hear from you. Just open a GitHub issue or create a pull request, and let’s start a conversation. xvi | Preface