[
  {
    "path": "LICENSE",
    "content": "Creative Commons Legal Code\n\nCC0 1.0 Universal\n\n    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE\n    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN\n    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS\n    INFORMATION ON AN \"AS-IS\" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES\n    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS\n    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM\n    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED\n    HEREUNDER.\n\nStatement of Purpose\n\nThe laws of most jurisdictions throughout the world automatically confer\nexclusive Copyright and Related Rights (defined below) upon the creator\nand subsequent owner(s) (each and all, an \"owner\") of an original work of\nauthorship and/or a database (each, a \"Work\").\n\nCertain owners wish to permanently relinquish those rights to a Work for\nthe purpose of contributing to a commons of creative, cultural and\nscientific works (\"Commons\") that the public can reliably and without fear\nof later claims of infringement build upon, modify, incorporate in other\nworks, reuse and redistribute as freely as possible in any form whatsoever\nand for any purposes, including without limitation commercial purposes.\nThese owners may contribute to the Commons to promote the ideal of a free\nculture and the further production of creative, cultural and scientific\nworks, or to gain reputation or greater distribution for their Work in\npart through the use and efforts of others.\n\nFor these and/or other purposes and motivations, and without any\nexpectation of additional consideration or compensation, the person\nassociating CC0 with a Work (the \"Affirmer\"), to the extent that he or she\nis an owner of Copyright and Related Rights in the Work, voluntarily\nelects to apply CC0 to the Work and publicly distribute the Work under its\nterms, with knowledge of his or her Copyright and Related Rights in the\nWork and the meaning and intended legal effect of CC0 on those rights.\n\n1. Copyright and Related Rights. A Work made available under CC0 may be\nprotected by copyright and related or neighboring rights (\"Copyright and\nRelated Rights\"). Copyright and Related Rights include, but are not\nlimited to, the following:\n\n  i. the right to reproduce, adapt, distribute, perform, display,\n     communicate, and translate a Work;\n ii. moral rights retained by the original author(s) and/or performer(s);\niii. publicity and privacy rights pertaining to a person's image or\n     likeness depicted in a Work;\n iv. rights protecting against unfair competition in regards to a Work,\n     subject to the limitations in paragraph 4(a), below;\n  v. rights protecting the extraction, dissemination, use and reuse of data\n     in a Work;\n vi. database rights (such as those arising under Directive 96/9/EC of the\n     European Parliament and of the Council of 11 March 1996 on the legal\n     protection of databases, and under any national implementation\n     thereof, including any amended or successor version of such\n     directive); and\nvii. other similar, equivalent or corresponding rights throughout the\n     world based on applicable law or treaty, and any national\n     implementations thereof.\n\n2. Waiver. To the greatest extent permitted by, but not in contravention\nof, applicable law, Affirmer hereby overtly, fully, permanently,\nirrevocably and unconditionally waives, abandons, and surrenders all of\nAffirmer's Copyright and Related Rights and associated claims and causes\nof action, whether now known or unknown (including existing as well as\nfuture claims and causes of action), in the Work (i) in all territories\nworldwide, (ii) for the maximum duration provided by applicable law or\ntreaty (including future time extensions), (iii) in any current or future\nmedium and for any number of copies, and (iv) for any purpose whatsoever,\nincluding without limitation commercial, advertising or promotional\npurposes (the \"Waiver\"). Affirmer makes the Waiver for the benefit of each\nmember of the public at large and to the detriment of Affirmer's heirs and\nsuccessors, fully intending that such Waiver shall not be subject to\nrevocation, rescission, cancellation, termination, or any other legal or\nequitable action to disrupt the quiet enjoyment of the Work by the public\nas contemplated by Affirmer's express Statement of Purpose.\n\n3. Public License Fallback. Should any part of the Waiver for any reason\nbe judged legally invalid or ineffective under applicable law, then the\nWaiver shall be preserved to the maximum extent permitted taking into\naccount Affirmer's express Statement of Purpose. In addition, to the\nextent the Waiver is so judged Affirmer hereby grants to each affected\nperson a royalty-free, non transferable, non sublicensable, non exclusive,\nirrevocable and unconditional license to exercise Affirmer's Copyright and\nRelated Rights in the Work (i) in all territories worldwide, (ii) for the\nmaximum duration provided by applicable law or treaty (including future\ntime extensions), (iii) in any current or future medium and for any number\nof copies, and (iv) for any purpose whatsoever, including without\nlimitation commercial, advertising or promotional purposes (the\n\"License\"). The License shall be deemed effective as of the date CC0 was\napplied by Affirmer to the Work. Should any part of the License for any\nreason be judged legally invalid or ineffective under applicable law, such\npartial invalidity or ineffectiveness shall not invalidate the remainder\nof the License, and in such case Affirmer hereby affirms that he or she\nwill not (i) exercise any of his or her remaining Copyright and Related\nRights in the Work or (ii) assert any associated claims and causes of\naction with respect to the Work, in either case contrary to Affirmer's\nexpress Statement of Purpose.\n\n4. Limitations and Disclaimers.\n\n a. No trademark or patent rights held by Affirmer are waived, abandoned,\n    surrendered, licensed or otherwise affected by this document.\n b. Affirmer offers the Work as-is and makes no representations or\n    warranties of any kind concerning the Work, express, implied,\n    statutory or otherwise, including without limitation warranties of\n    title, merchantability, fitness for a particular purpose, non\n    infringement, or the absence of latent or other defects, accuracy, or\n    the present or absence of errors, whether or not discoverable, all to\n    the greatest extent permissible under applicable law.\n c. Affirmer disclaims responsibility for clearing rights of other persons\n    that may apply to the Work or any use thereof, including without\n    limitation any person's Copyright and Related Rights in the Work.\n    Further, Affirmer disclaims responsibility for obtaining any necessary\n    consents, permissions or other rights required for any use of the\n    Work.\n d. Affirmer understands and acknowledges that Creative Commons is not a\n    party to this document and has no duty or obligation with respect to\n    this CC0 or use of the Work.\n"
  },
  {
    "path": "README.md",
    "content": "<p align=\"center\"><img src=\"images/how_they_devops.png\"/></p>\n\n> A curated collection of publicly available resources on how companies around the world practice DevOps\n\n## Introduction\n\n__How They DevOps__ is a curated knowledge repository on DevOps related topics - CI/CD\n\nThere are many ways to practice DevOps. Fortunately, many companies are willing to share how they do it. I believe there is much to learn from this documented use cases and published resources. The content you'll find in this repository is a list of such resources.\n\nThe reosurces are indexed by companies, technologies, years and DevOps related topics\n\nHappy Learning!\n\n*Please note, that all the resources mentioned here are publicly available resources.*\n\n## By Company\n<details>\n  <summary>Adzuna</summary>\n\n#### Articles\n* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 1 - 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-1-588d8254f0b3)\n* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 2 - 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-2-4d0ce7b63f2a)\n</details>\n\n<details>\n  <summary>Airbnb</summary>\n\n#### Podcasts\n* [Continuous Delivery at Airbnb - 2019](https://devops.com/devops-chat-continuous-delivery-at-airbnb)\n</details>\n\n<details>\n  <summary>Amazon</summary>\n\n#### Articles\n* [What is DevOps?](https://aws.amazon.com/devops/what-is-devops)\n* [DevOps Resources](https://aws.amazon.com/devops/resources)\n\n#### Blog\n* [AWS DevOps Blog](https://aws.amazon.com/blogs/devops/)\n\n</details>\n\n<details>\n  <summary>Atlassian</summary>\n\n#### Articles\n* [What is DevOps?](https://www.atlassian.com/devops)\n\n#### Blogs\n* [Atlassian DevOps Blog](https://www.atlassian.com/blog/devops)\n* [DevOps Best Practices](https://www.atlassian.com/solutions/devops/best-practices)\n</details>\n\n<details>\n  <summary>Carwow</summary>\n\n#### Articles\n* [Speeding up our deploys by ~35% - 2019](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)\n</details>\n\n<details>\n  <summary>Cinglevue</summary>\n\n#### Articles\n* [DevOps: How to build an efficient CI/CD pipeline - 2019](https://medium.com/developers-coffee/how-to-build-an-efficient-ci-cd-pipeline-b5738ad567c8)\n</details>\n\n<details>\n  <summary>CloudBees</summary>\n\n#### Articles\n* [DevOps Best Practices: Opinionated Software That Drives a Successful DevOps Culture - 2021](https://www.cloudbees.com/blog/devops-best-practices)\n* [8 DevOps Tools You Should Use for Opinionated, Cloud Native App Development - 2021](https://www.cloudbees.com/blog/devops-tools-cloud-native-development)\n* [Continuous Verification, AKA Just Doing DevOps - 2020](https://www.cloudbees.com/blog/continuous-verification)\n\n#### Blog\n* [CloudBees Blog](https://www.cloudbees.com/blog)\n\n</details>\n\n<details>\n  <summary>Codefresh</summary>\n\n#### Articles\n* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)\n* [Using Google Container Registry To Invoke Codefresh Pipelines - 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)\n* [What Is Zero Trust & How Do We Implement It to Run Secure CI/CD Workflows in Kubernetes? - 2021](https://codefresh.io/security-testing/codefresh-runner-overview)\n* [Kubernetes Deployment Antipatterns – part 1 - 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-1)\n* [Kubernetes Deployment Antipatterns – part 2 - 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-2)\n* [Kubernetes Deployment Antipatterns – part 3 - 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-3)\n#### Blogs\n* [Codefresh blog](https://codefresh.io/blog)\n</details>\n\n<details>\n  <summary>Facebook</summary>\n\n#### Articles\n* [Rapid release at massive scale](https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale)\n\n#### Blog\n* [Facebook Engineering Blog](https://engineering.fb.com)\n</details>\n\n<details>\n  <summary>Grandcentrix</summary>\n\n#### Articles\n* [How we use Jenkins Pipeline to standardize our Continuous Integration - 2019](https://medium.com/grandcentrix/how-we-use-jenkins-pipeline-to-simplify-our-continuous-integration-4fb462b0c15c)\n</details>\n\n<details>\n  <summary>Hootsuite</summary>\n\n#### Articles\n* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)\n</details>\n\n<details>\n  <summary>Kalisio</summary>\n\n#### Articles\n* [Why We Stopped Using So-Called Best Practices in Our CI/CD Process - 2019](https://medium.com/better-programming/why-we-stopped-using-so-called-best-practices-in-our-ci-cd-process-2ff09811f633)\n</details>\n\n<details>\n  <summary>Kitabisa</summary>\n\n#### Articles\n* [Our CI/CD Journey — from Monolith to Micro-Services - 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)\n</details>\n\n<details>\n  <summary>Lyft</summary>\n\n#### Articles\n* [Continuous Deployment at Lyft - 2022](https://eng.lyft.com/continuous-deployment-at-lyft-9b457314771a)\n</details>\n\n<details>\n  <summary>Microsoft</summary>\n\n#### Articles\n* [What is DevOps?](https://docs.microsoft.com/en-us/azure/devops/learn/what-is-devops)\n\n#### Blog\n* [Azure DevOps Blog](https://devblogs.microsoft.com/devops)\n\n</details>\n\n<details>\n  <summary>Netflix</summary>\n\n#### Articles\n* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)\n* [Lumen: Custom, Self-Service Dashboarding For Netflix](https://netflixtechblog.com/lumen-custom-self-service-dashboarding-for-netflix-8c56b541548c)\n* [Netflix Cloud Security: Detecting Credential Compromise in AWS - 2018](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)\n\n#### Blog\n* [DevOps Blog](https://netflixtechblog.com/tagged/devops)\n</details>\n\n<details>\n  <summary>90 Seconds</summary>\n\n#### Articles\n* [Lessons learned with Gitlab Runner on Kubernetes - 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)\n</details>\n\n<details>\n  <summary>Opendoor</summary>\n\n#### Articles\n* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)\n</details>\n\n<details>\n  <summary>Oursky</summary>\n\n#### Articles\n* [Battle Tested: How We Built and Master Our CI/CD Pipeline - 2019](https://m.oursky.com/battle-tested-how-we-built-and-master-our-ci-cd-pipeline-2ce99c9b2fa4)\n</details>\n\n<details>\n  <summary>Pixel Point</summary>\n\n#### Articles\n* [Tips and tricks for scalable CI/CD flow - 2018](https://medium.com/pixelpoint/tips-and-tricks-for-scalable-ci-cd-flow-5fa9dd457f22)\n</details>\n\n<details>\n  <summary>Prismic</summary>\n\n#### Articles\n* [We deploy everyday and this is how!](https://medium.com/@prismicio/we-deploy-everyday-and-this-is-how-6a5fc8fb0e2e)\n</details>\n\n<details>\n  <summary>Red Hat</summary>\n\n#### Articles\n* [Who is a DevOps Engineer?](https://www.redhat.com/en/topics/devops/devops-engineer)\n* [What is DevOps?](https://www.redhat.com/en/topics/devops)\n* [What is DevSecOps?](https://www.redhat.com/en/topics/devops/what-is-devsecops)\n* [You call that DevSecOps? Why your DevSecOps practice may be falling short](https://www.redhat.com/en/blog/devsecops-reducing-risk-and-increasing-agility)\n* [What is a CI/CD pipeline? - Red Hat](https://www.redhat.com/en/topics/devops/what-cicd-pipeline)\n\n#### Books\n* [Free - DevOps with OpenShift](https://developers.redhat.com/topics/devops)\n</details>\n\n<details>\n  <summary>Riskified</summary>\n\n#### Articles\n* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)\n\n</details>\n\n<details>\n  <summary>Slack</summary>\n\n#### Articles\n* [How we use Terraform at Slack - 2022](https://slack.engineering/how-we-use-terraform-at-slack/)\n* [Development Environments at Slack - 2020](https://slack.engineering/development-environments-at-slack/)\n* [Deploys at Slack - 2020](https://slack.engineering/deploys-at-slack/)\n</details>\n\n<details>\n  <summary>Trendyol</summary>\n\n#### Articles\n* [Dependency Check at CI/CD Pipeline - 2020](https://medium.com/trendyol-tech/dependency-check-at-ci-cd-pipeline-17020e15b391)\n</details>\n\n<details>\n  <summary>Uber</summary>\n\n#### Articles\n* [Security at Speed: Modern Security and DevOps](https://medium.com/uber-security-privacy/speed-security-devops-7f3ee7e5a2ae)\n* [Introducing Makisu: Uber’s Fast, Reliable Docker Image Builder for Apache Mesos and Kubernetes](https://eng.uber.com/makisu/)\n\n#### Blog\n* [Uber Engineering Blog](https://eng.uber.com)\n</details>\n\n<details>\n  <summary>Verizon</summary>\n\n#### Articles\n* [How our CI/CD workflow provides a model for other CDNs - 2018](https://vzmediaplatform.medium.com/how-our-ci-cd-workflow-provides-a-model-for-other-cdns-65f9f765b32a)\n</details>\n\n<details>\n  <summary>Wildlife Studios</summary>\n\n#### Articles\n* [How we improved our CI/CD pipelines over the years - 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)\n</details>\n\n<details>\n  <summary>XETICS</summary>\n\n#### Articles\n* [Our story with Flutter and Gitlab-Ci - 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)\n</details>\n\n## By Technology\n\n<details>\n  <summary>CircleCI</summary>\n\n#### Articles\n* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)\n* [Our CI/CD Journey — from Monolith to Micro-Services - Kitabisa, 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)\n</details>\n\n<details>\n  <summary>Codefresh</summary>\n\n#### Articles\n* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - Codefresh, 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)\n* [Using Google Container Registry To Invoke Codefresh Pipelines - Codefresh, 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)\n</details>\n\n<details>\n  <summary>GitLab</summary>\n\n#### Articles\n* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds, 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)\n* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)\n* [Our story with Flutter and Gitlab-Ci - XETICS, 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)\n</details>\n\n<details>\n  <summary>Heroku</summary>\n\n#### Articles\n* [Speeding up our deploys by ~35% - Carwow, 2019](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)\n* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)\n</details>\n\n<details>\n  <summary>Jenkins</summary>\n\n#### Articles\n* [How we use Jenkins Pipeline to standardize our Continuous Integration - Grandcentrix, 2019](https://medium.com/grandcentrix/how-we-use-jenkins-pipeline-to-simplify-our-continuous-integration-4fb462b0c15c)\n* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)\n</details>\n\n<details>\n  <summary>Kubernetes</summary>\n\n#### Articles\n* [Kubernetes Deployment Antipatterns – part 1 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-1)\n* [Kubernetes Deployment Antipatterns – part 2 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-2)\n* [Kubernetes Deployment Antipatterns – part 3 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-3)\n* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)\n* [Introducing Makisu: Uber’s Fast, Reliable Docker Image Builder for Apache Mesos and Kubernetes - Uber](https://eng.uber.com/makisu/)\n* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)\n* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds, 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)\n* [Our CI/CD Journey — from Monolith to Micro-Services - Kitabisa, 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)\n* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)\n</details>\n\n<details>\n  <summary>OpenShift</summary>\n\n#### Books\n* [Free - DevOps with OpenShift](https://developers.redhat.com/topics/devops)\n</details>\n\n<details>\n  <summary>Packer</summary>\n\n#### Articles\n* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)\n</details>\n\n<details>\n  <summary>Rails</summary>\n\n#### Articles\n* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)\n</details>\n\n<details>\n  <summary>Travis CI</summary>\n\n#### Articles\n* [Why We Stopped Using So-Called Best Practices in Our CI/CD Process - Kalisio, 2019](https://medium.com/better-programming/why-we-stopped-using-so-called-best-practices-in-our-ci-cd-process-2ff09811f633)\n</details>\n\n<details>\n  <summary>Windows</summary>\n\n#### Articles\n* [Applying Netflix DevOps Patterns to Windows](https://netflixtechblog.com/applying-netflix-devops-patterns-to-windows-2a57f2dbbf79)\n</details>\n\n## By Category\n\n<details>\n  <summary>DevOps</summary>\n\n#### Articles\n* [What is DevOps? - Amazon](https://aws.amazon.com/devops/what-is-devops)\n* [What is DevOps? - Atlassian](https://www.atlassian.com/devops)\n* [What is DevOps? - Microsoft](https://docs.microsoft.com/en-us/azure/devops/learn/what-is-devops)\n* [What is DevOps? - Red Hat](https://www.redhat.com/en/topics/devops)\n* [DevOps Best Practices: Opinionated Software That Drives a Successful DevOps Culture - CloudBees, 2021](https://www.cloudbees.com/blog/devops-best-practices)\n* [8 DevOps Tools You Should Use for Opinionated, Cloud Native App Development - CloudBees, 2021](https://www.cloudbees.com/blog/devops-tools-cloud-native-development)\n* [Continuous Verification, AKA Just Doing DevOps - CloudBees, 2020](https://www.cloudbees.com/blog/continuous-verification)\n\n</details>\n\n<details>\n  <summary>AWS</summary>\n\n#### Articles\n* [Netflix Cloud Security: Detecting Credential Compromise in AWS - 2018](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)\n</details>\n\n<details>\n  <summary>CI/CD</summary>\n\n#### Articles - How companies practice and apply CI/CD\n* [What Is Zero Trust & How Do We Implement It to Run Secure CI/CD Workflows in Kubernetes? - Codefresh, 2021](https://codefresh.io/security-testing/codefresh-runner-overview)\n* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence - Riskified, 2020](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)\n* [We deploy everyday and this is how! - Prismic, 2017](https://medium.com/@prismicio/we-deploy-everyday-and-this-is-how-6a5fc8fb0e2e)\n* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 1 - Adzuna, 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-1-588d8254f0b3)\n* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 2 - Adzuna, 2018](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-2-4d0ce7b63f2a)\n* [Continuous Delivery at Airbnb - 2019](https://devops.com/devops-chat-continuous-delivery-at-airbnb)\n* [Battle Tested: How We Built and Master Our CI/CD Pipeline - Oursky, 2019](https://m.oursky.com/battle-tested-how-we-built-and-master-our-ci-cd-pipeline-2ce99c9b2fa4)\n* [How we use Jenkins Pipeline to standardize our Continuous Integration - Grandcentrix, 2019](https://medium.com/grandcentrix/how-we-use-jenkins-pipeline-to-simplify-our-continuous-integration-4fb462b0c15c)\n* [How We Got To Continuous Deployment With Rails, CircleCI, and Heroku - Opendoor, 2017](https://medium.com/opendoor-labs/continuous-deployment-with-rails-circleci-and-heroku-314635d800c6)\n* [Why We Stopped Using So-Called Best Practices in Our CI/CD Process - Kalisio, 2019](https://medium.com/better-programming/why-we-stopped-using-so-called-best-practices-in-our-ci-cd-process-2ff09811f633)\n* [How our CI/CD workflow provides a model for other CDNs - Verizon, 2018](https://vzmediaplatform.medium.com/how-our-ci-cd-workflow-provides-a-model-for-other-cdns-65f9f765b32a)\n* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds, 2019](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)\n* [DevOps: How to build an efficient CI/CD pipeline - Cinglevue, 2019](https://medium.com/developers-coffee/how-to-build-an-efficient-ci-cd-pipeline-b5738ad567c8)\n* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)\n* [Our CI/CD Journey — from Monolith to Micro-Services - Kitabisa, 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)\n* [Speeding up our deploys by ~35% - Carwow, 2019](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)\n* [Our story with Flutter and Gitlab-Ci - XETICS, 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)\n* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)\n\n#### Articles - Learn about CI/CD\n* [What is a CI/CD pipeline? - Red Hat](https://www.redhat.com/en/topics/devops/what-cicd-pipeline)\n* [Tips and tricks for scalable CI/CD flow - Pixel Point, 2018](https://medium.com/pixelpoint/tips-and-tricks-for-scalable-ci-cd-flow-5fa9dd457f22)\n\n#### Articles - CI/CD with company products\n* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - Codefresh, 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)\n* [Using Google Container Registry To Invoke Codefresh Pipelines - Codefresh, 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)\n\n#### Books\n* [Free - DevOps with OpenShift](https://developers.redhat.com/topics/devops)\n</details>\n\n<details>\n  <summary>Dashboards</summary>\n\n#### Articles\n* [Lumen: Custom, Self-Service Dashboarding For Netflix](https://netflixtechblog.com/lumen-custom-self-service-dashboarding-for-netflix-8c56b541548c)\n</details>\n\n<details>\n  <summary>DevSecOps</summary>\n\n#### Articles\n* [What is DevSecOps? - Red Hat](https://www.redhat.com/en/topics/devops/what-is-devsecops)\n* [You call that DevSecOps? Why your DevSecOps practice may be falling short - Red Hat](https://www.redhat.com/en/blog/devsecops-reducing-risk-and-increasing-agility)\n* [Security at Speed: Modern Security and DevOps - Uber, 2017](https://medium.com/uber-security-privacy/speed-security-devops-7f3ee7e5a2ae)\n* [Netflix Cloud Security: Detecting Credential Compromise in AWS - Netflix, 2018](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)\n* [DevSecOps: Making Security Central To Your DevOps Pipeline - Spacelift](https://spacelift.io/blog/what-is-devsecops)\n</details>\n\n<details>\n  <summary>Release</summary>\n\n#### Articles\n* [Rapid release at massive scale - Facebook, 2017](https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale)\n</details>\n\n## By Year\n\n<details>\n  <summary>2021</summary>\n\n#### Articles\n* [CI/CD Pipelines for Kubernetes Apps with Pulumi & Codefresh - Codefresh, 2021](https://codefresh.io/webinars/ci-cd-pipelines-kubernetes-apps-pulumi-codefresh)\n* [Using Google Container Registry To Invoke Codefresh Pipelines - Codefresh, 2021](https://codefresh.io/continuous-integration/using-google-container-registry-invoke-codefresh-pipelines/)\n* [What Is Zero Trust & How Do We Implement It to Run Secure CI/CD Workflows in Kubernetes? - Codefresh, 2021](https://codefresh.io/security-testing/codefresh-runner-overview)\n* [Kubernetes Deployment Antipatterns – part 1 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-1)\n* [Kubernetes Deployment Antipatterns – part 2 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-2)\n* [Kubernetes Deployment Antipatterns – part 3 - Codefresh, 2021](https://codefresh.io/kubernetes-tutorial/kubernetes-antipatterns-3)\n* [DevOps Best Practices: Opinionated Software That Drives a Successful DevOps Culture - CloudBees](https://www.cloudbees.com/blog/devops-best-practices)\n* [8 DevOps Tools You Should Use for Opinionated, Cloud Native App Development - CloudBees](https://www.cloudbees.com/blog/devops-tools-cloud-native-development)\n</details>\n\n<details>\n  <summary>2020</summary>\n\n#### Articles\n* [Dependency Check at CI/CD Pipeline - Trendyol](https://medium.com/trendyol-tech/dependency-check-at-ci-cd-pipeline-17020e15b391)\n* [How to Build a CI/CD Process That Deploys on Kubernetes and Focuses on Developer Independence - Riskified](https://medium.com/riskified-technology/how-to-build-a-ci-cd-process-that-deploys-on-kubernetes-and-focuses-on-developer-independence-7dc4c20984a)\n* [Continuous Verification, AKA Just Doing DevOps - CloudBees](https://www.cloudbees.com/blog/continuous-verification)\n* [How we improved our CI/CD pipelines over the years - Wildlife Studios, 2020](https://medium.com/tech-at-wildlife-studios/how-we-built-a-ci-cd-that-makes-developers-happy-2222f02ab29)\n* [Our CI/CD Journey — from Monolith to Micro-Services - 2020](https://medium.com/@ardityawahyu/our-ci-cd-journey-from-monolith-to-micro-servives-9e6787dc7274)\n</details>\n\n<details>\n  <summary>2019</summary>\n\n#### Podcasts\n* [Continuous Delivery at Airbnb](https://devops.com/devops-chat-continuous-delivery-at-airbnb)\n\n#### Articles\n* [Lessons learned with Gitlab Runner on Kubernetes - 90 seconds](https://medium.com/90seconds/lessons-learned-with-gitlab-runner-on-kubernetes-d547c30ad5fb)\n* [DevOps: How to build an efficient CI/CD pipeline - Cinglevue](https://medium.com/developers-coffee/how-to-build-an-efficient-ci-cd-pipeline-b5738ad567c8)\n* [Speeding up our deploys by ~35% - Carwow](https://medium.com/carwow-product-engineering/speeding-up-our-heroku-deploys-by-35-percent-f9fa6f6cf404)\n* [Our story with Flutter and Gitlab-Ci - XETICS, 2019](https://medium.com/@fezu54/our-story-with-flutter-and-gitlab-ci-26bd40c26155)\n</details>\n\n<details>\n  <summary>2018</summary>\n\n#### Articles\n* [Netflix Cloud Security: Detecting Credential Compromise in AWS - Netflix](https://netflixtechblog.com/netflix-cloud-security-detecting-credential-compromise-in-aws-9493d6fd373a)\n* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 1 - Adzuna](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-1-588d8254f0b3)\n* [Continuous Integration and Continuous Delivery with BitBucket Pipelines — Part 2 - Adzuna](https://medium.com/adzuna-engineering/continuous-integration-and-continuous-delivery-with-bitbucket-pipelines-part-2-4d0ce7b63f2a)\n* [Tips and tricks for scalable CI/CD flow - Pixel Point](https://medium.com/pixelpoint/tips-and-tricks-for-scalable-ci-cd-flow-5fa9dd457f22)\n* [How our CI/CD workflow provides a model for other CDNs - Verizon](https://vzmediaplatform.medium.com/how-our-ci-cd-workflow-provides-a-model-for-other-cdns-65f9f765b32a)\n* [Jenkins, Kubernetes, and Hashicorp Vault - 2018](https://medium.com/hootsuite-engineering/jenkins-kubernetes-and-hashicorp-vault-c2011bd2d66c)\n</details>\n\n<details>\n  <summary>2017</summary>\n\n#### Articles\n* [Rapid release at massive scale - Facebook](https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale)\n* [Security at Speed: Modern Security and DevOps - Uber](https://medium.com/uber-security-privacy/speed-security-devops-7f3ee7e5a2ae)\n* [We deploy everyday and this is how! - Prismic](https://medium.com/@prismicio/we-deploy-everyday-and-this-is-how-6a5fc8fb0e2e)\n</details>\n\n### More Infra & DevOps projects\n\n<p align=\"center\"><a href=\"https://github.com/bregman-arie/devops-exercises\"><img src=\"images/devops_exercises.png\"/></a></p>\n<p align=\"center\"><a href=\"https://github.com/bregman-arie/devops-resources\"><img src=\"images/devops_resources.png\"/></a></p>\n<p align=\"center\"><a href=\"https://github.com/bregman-arie/infraverse\"><img src=\"images/infraverse.png\"/></a></p>\n\n### Credits\n* Inspired by [Howtheytest](https://github.com/abhivaikar/howtheytest) from [Abhijeet Vaikar](https://github.com/abhivaikar)\n\n### Contribute\nContributions welcome! Read the [contribution guidelines](contributing.md) first.\n\n### License\n[![CC0](https://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0)\n"
  },
  {
    "path": "code-of-conduct.md",
    "content": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nIn the interest of fostering an open and welcoming environment, we as\ncontributors and maintainers pledge to making participation in our project and\nour community a harassment-free experience for everyone, regardless of age, body\nsize, disability, ethnicity, gender identity and expression, level of experience,\nnationality, personal appearance, race, religion, or sexual identity and\norientation.\n\n## Our Standards\n\nExamples of behavior that contributes to creating a positive environment\ninclude:\n\n* Using welcoming and inclusive language\n* Being respectful of differing viewpoints and experiences\n* Gracefully accepting constructive criticism\n* Focusing on what is best for the community\n* Showing empathy towards other community members\n\nExamples of unacceptable behavior by participants include:\n\n* The use of sexualized language or imagery and unwelcome sexual attention or\nadvances\n* Trolling, insulting/derogatory comments, and personal or political attacks\n* Public or private harassment\n* Publishing others' private information, such as a physical or electronic\n  address, without explicit permission\n* Other conduct which could reasonably be considered inappropriate in a\n  professional setting\n\n## Our Responsibilities\n\nProject maintainers are responsible for clarifying the standards of acceptable\nbehavior and are expected to take appropriate and fair corrective action in\nresponse to any instances of unacceptable behavior.\n\nProject maintainers have the right and responsibility to remove, edit, or\nreject comments, commits, code, wiki edits, issues, and other contributions\nthat are not aligned to this Code of Conduct, or to ban temporarily or\npermanently any contributor for other behaviors that they deem inappropriate,\nthreatening, offensive, or harmful.\n\n## Scope\n\nThis Code of Conduct applies both within project spaces and in public spaces\nwhen an individual is representing the project or its community. Examples of\nrepresenting a project or community include using an official project e-mail\naddress, posting via an official social media account, or acting as an appointed\nrepresentative at an online or offline event. Representation of a project may be\nfurther defined and clarified by project maintainers.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be\nreported by contacting the project team at upgundecha@gmail.com. All\ncomplaints will be reviewed and investigated and will result in a response that\nis deemed necessary and appropriate to the circumstances. The project team is\nobligated to maintain confidentiality with regard to the reporter of an incident.\nFurther details of specific enforcement policies may be posted separately.\n\nProject maintainers who do not follow or enforce the Code of Conduct in good\nfaith may face temporary or permanent repercussions as determined by other\nmembers of the project's leadership.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,\navailable at [http://contributor-covenant.org/version/1/4][version]\n\n[homepage]: http://contributor-covenant.org\n[version]: http://contributor-covenant.org/version/1/4/\n"
  },
  {
    "path": "contributing.md",
    "content": "# Contribution Guidelines\n\nPlease note that this project is released with a\n[Contributor Code of Conduct](code-of-conduct.md). By participating in this\nproject you agree to abide by its terms.\n\n---\nPlease feel free to fork the repo and add blog posts, videos, incidents reports or any other useful resource to the repo.\n\nYou may find the [Markdown Link Generator](https://chrome.google.com/webstore/detail/markdown-link-generator/glnecdafikgonniihbdjneaikhcgcbhb?hl=en) extension for Google Chrome Browser easy to generate links in Markdown inline text link format. This tool will help to generate links for resources with minimal steps and context switching.\n\nEnsure your pull request adheres to the following guidelines:\n\n- Make sure the high level list is alphabetically ordered\n\nThank you for your suggestions!\n\n\n## Updating your PR\n\nA lot of times, making a PR adhere to the standards above can be difficult.\nIf the maintainers notice anything that we'd like changed, we'll ask you to\nedit your PR before we merge it. There's no need to open a new PR, just edit\nthe existing one. If you're not sure how to do that,\n[here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)\non the different ways you can update your PR so that we can merge it.\n"
  }
]