mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-05-05 16:56:37 +00:00
new entries
This commit is contained in:
Inaki Fernandez
@@ -4,6 +4,7 @@
|
||||
- [Kubectl Cheat Sheets](#kubectl-cheat-sheets)
|
||||
- [Docker Cheat Sheets](#docker-cheat-sheets)
|
||||
- [Git and GitHub Cheat Sheets](#git-and-github-cheat-sheets)
|
||||
- [Git Flow Cheat Sheets](#git-flow-cheat-sheets)
|
||||
- [Ansible Cheat Sheets](#ansible-cheat-sheets)
|
||||
- [Packer and Terraform Cheat Sheets](#packer-and-terraform-cheat-sheets)
|
||||
- [Linux Command Cheat Sheets](#linux-command-cheat-sheets)
|
||||
@@ -61,6 +62,9 @@
|
||||
* [rogerdudler.github.io: git - the simple guide 🌟](https://rogerdudler.github.io/git-guide) Just a simple guide for getting started with git. no deep shit ;)
|
||||
* [rogerdudler.github.io: git cheat sheet pdf](https://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf)
|
||||
|
||||
### Git Flow Cheat Sheets
|
||||
* [Git-flow cheatsheet](https://danielkummer.github.io/git-flow-cheatsheet/index.html)
|
||||
|
||||
## Ansible Cheat Sheets
|
||||
* [Ansible Roles Explained | Cheat Sheet](https://linuxacademy.com/blog/red-hat/ansible-roles-explained/)
|
||||
* [edureka.co: Ansible Cheat Sheet – A DevOps Quick Start Guide](https://www.edureka.co/blog/cheatsheets/ansible-cheat-sheet-guide/)
|
||||
|
||||
@@ -10,6 +10,7 @@
|
||||
- [Cloud Native Development Architectural Diagrams Demos](#cloud-native-development-architectural-diagrams-demos)
|
||||
- [OpenShift Demos](#openshift-demos)
|
||||
- [Knative](#knative)
|
||||
- [OpenShift Pipelines Workshop (Tekton)](#openshift-pipelines-workshop-tekton)
|
||||
- [Jenkins Demos](#jenkins-demos)
|
||||
- [Jenkins Declarative Pipelines with OpenShift](#jenkins-declarative-pipelines-with-openshift)
|
||||
- [OpenShift Pipelines with S2i and Jenkins Blue Ocean](#openshift-pipelines-with-s2i-and-jenkins-blue-ocean)
|
||||
@@ -96,6 +97,11 @@
|
||||
### Knative
|
||||
* [knative-tutorial](https://github.com/redhat-developer-demos/knative-tutorial) A pratical guide to get started with knative. Knative concepts are explained simple and easy way with lots of demos and exercises.
|
||||
|
||||
### OpenShift Pipelines Workshop (Tekton)
|
||||
- [openshift-pipelines-workshop](https://redhat-developer-demos.github.io/openshift-pipelines-workshop/) Workshop to demonstrate OpenShift Pipelines (featuring Tekton)
|
||||
- [Build a Go application using OpenShift Pipelines](https://developers.redhat.com/blog/2020/05/26/build-a-go-application-using-openshift-pipelines/)
|
||||
- [OpenShift Pipelines Catalog](https://github.com/openshift/pipelines-catalog)
|
||||
|
||||
## Jenkins Demos
|
||||
* [kublr.com: cicd pipeline with jenkins nexus kubernetes](https://kublr.com/blog/cicd-pipeline-with-jenkins-nexus-kubernetes/)
|
||||
* [bitbucket.org: setting up a cicd pipeline with spring mvc and kubernetes on aws](https://bitbucket.org/blog/setting-up-a-ci-cd-pipeline-with-spring-mvc-jenkins-and-kubernetes-on-aws )
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# DevOps
|
||||
- [Introduction to Digital Business Transformation](#introduction-to-digital-business-transformation)
|
||||
- [DevOps](#devops)
|
||||
- [Blogs](#blogs)
|
||||
- [Xebia Labs and DevOps](#xebia-labs-and-devops)
|
||||
- [Netflix and DevOps](#netflix-and-devops)
|
||||
- [Public Cloud DevOps](#public-cloud-devops)
|
||||
@@ -28,6 +29,11 @@
|
||||
* [dzone: Are You Stuck in the New DevOps Matrix From Hell? 🌟](https://dzone.com/articles/are-you-stuck-in-the-new-devops-matrix-from-hell) See how Docker solved the matrix-from-hell problem, and how DevOps techniques can help avoid the config sprawl that comes with microservices.
|
||||
* [kenmugrage.com 🌟](https://kenmugrage.com/2017/05/05/my-new-definition-of-devops/#more-4) DevOps: A culture where people, regardless of title or background, work together to imagine, develop, deploy and operate a system.
|
||||
|
||||
## Blogs
|
||||
- [devops.com](https://devops.com/)
|
||||
- [devopscube.com](https://devopscube.com/)
|
||||
- [devopszone.info](https://www.devopszone.info/)
|
||||
|
||||
## Xebia Labs and DevOps
|
||||
- [DevOps Glosary of Terms 🌟](https://xebialabs.com/glossary/)
|
||||
- [The Ultimate DevOps Tool Chest 🌟](https://xebialabs.com/the-ultimate-devops-tool-chest/)
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
|
||||
## Introduction
|
||||
- [fiercesw.com: DevOps vs DevSecOps](https://fiercesw.com/devsecops-starter)
|
||||
- [DevSecOps Explained](https://www.devopszone.info/post/devsecops-explained)
|
||||
|
||||
## Project Calico
|
||||
* [Project Calico](https://www.projectcalico.org/) Secure networking for the cloud native era
|
||||
|
||||
@@ -95,15 +95,16 @@ It prescribes that software designers should define formal, precise and verifiab
|
||||
|
||||
#### Git Flow
|
||||
* One of the main concepts of **GitFlow** is **feature branches**. The idea is that each feature should be developed in its own branch. When the feature is done, it gets merged into develop branch.
|
||||
* [devopszone.info: An Introduction To Git-flow Workflow](https://www.devopszone.info/post/an-introduction-to-git-flow-workflow)
|
||||
* [atlassian.com: Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)
|
||||
* [gitkraken.com: GitFlow](https://support.gitkraken.com/git-workflows-and-extensions/git-flow/) is a list of rules to keep a repo’s history organized, and is used to make the release process, bug fixes, and feature creation easier.
|
||||
* [git-flow.readthedocs.io](https://git-flow.readthedocs.io/)
|
||||
* [aprendegit.com: git-flow: la rama develop y uso de feature branches](http://aprendegit.com/git-flow-la-rama-develop-y-uso-de-feature-branches/)
|
||||
* [medium.com: Gitflow — Branch Guide](https://medium.com/@rafavinnce/gitflow-branch-guide-8a523360c053)
|
||||
* [medium.com: Git Flow for Beginners](https://medium.com/@thibault60000/git-flow-for-beginners-d7a152b2c1f9)
|
||||
* [medium.com: What is GitFlow?](https://medium.com/@okandavut/what-is-gitflow-c0be7a659992)
|
||||
* [gist.github.com/JamesMGreene: A comparison of using `git flow` commands versus raw `git` commands](https://gist.github.com/JamesMGreene/cdd0ac49f90c987e45ac)
|
||||
* [Git-flow cheatsheet](https://danielkummer.github.io/git-flow-cheatsheet/index.html)
|
||||
* [aprendegit.com: git-flow: la rama develop y uso de feature branches](http://aprendegit.com/git-flow-la-rama-develop-y-uso-de-feature-branches/)
|
||||
|
||||
### Trunk-based Development vs. Git Flow
|
||||
* [toptal.com: Trunk-based Development vs. Git Flow](https://www.toptal.com/software/trunk-based-development-git-flow)
|
||||
@@ -151,6 +152,7 @@ git push origin -f
|
||||
* [GitHub CLI](https://cli.github.com/)
|
||||
* [github.com/cli/cli](https://github.com/cli/cli)
|
||||
* [github.blog: GitHub CLI allows you to close, reopen, and add metadata to issues and pull requests](https://github.blog/changelog/2020-05-11-github-cli-allows-you-to-close-reopen-and-add-metadata-to-issues-and-pull-requests/)
|
||||
* [github.blog: Mark pull requests as ready for review, view the diff, review, and merge from GitHub CLI](https://github.blog/changelog/2020-05-26-mark-pull-requests-as-ready-for-review-review-and-merge-from-github-cli/)
|
||||
|
||||
## Git Tools
|
||||
* [Atlassian Sourcetree](https://www.sourcetreeapp.com/)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
# GitOps
|
||||
- [Introduction](#introduction)
|
||||
- [Git Repositories Structures](#git-repositories-structures)
|
||||
- [GitOps Tools](#gitops-tools)
|
||||
- [Flux. The GitOps Operator for Kubernetes](#flux-the-gitops-operator-for-kubernetes)
|
||||
- [WKSctl. Weave Kubernetes System Control](#wksctl-weave-kubernetes-system-control)
|
||||
@@ -20,6 +21,9 @@
|
||||
- [dzone: What Is GitOps, Really?](https://dzone.com/articles/what-is-gitops-really) This article will help you understand what GitOps really is as a strategy for development, and its benefits over other CI/CD approaches
|
||||
- [Continuous GitOps, the way to do DevOps in Kubernetes](https://medium.com/@imarunrk/continuous-gitops-the-way-to-do-devops-in-kubernetes-896b0ea1d0fb) Continuous GitOps, the new age DevOps practice to increase the delivery velocity by achieving an end to end “Git source of truth” with Zero manual changes into the Kubernetes cluster
|
||||
|
||||
## Git Repositories Structures
|
||||
- [GitOps: How to Ops Your Git the Right Way 🌟](https://dzone.com/articles/gitops-how-to-ops-your-git-the-right-way) In this article we’ll look into the specifics of creating Git repositories structures — the very core of the GitOps approach.
|
||||
|
||||
## GitOps Tools
|
||||
- [FluxCD, ArgoCD or Jenkins X: Which Is the Right GitOps Tool for You?](https://blog.container-solutions.com/fluxcd-argocd-or-jenkins-x-which-is-the-right-gitops-tool-for-you)
|
||||
- [slideshare: GitOps, Jenkins X & Future of CI/CD](https://slideshare.net/rakutentech/gitops-jenkins-x-future-of-cicd)
|
||||
|
||||
@@ -23,8 +23,10 @@
|
||||
- [Monitoring jenkins](#monitoring-jenkins)
|
||||
- [Jenkins and Spring Boot](#jenkins-and-spring-boot)
|
||||
- [Kubernetes Native Jenkins Operator](#kubernetes-native-jenkins-operator)
|
||||
- [CloudBees Rollout and Feature Flags](#cloudbees-rollout-and-feature-flags)
|
||||
- [Feature Flags in CloudBees Enterprise On-Premise](#feature-flags-in-cloudbees-enterprise-on-premise)
|
||||
- [CloudBees](#cloudbees)
|
||||
- [CloudBees Rollout and Feature Flags](#cloudbees-rollout-and-feature-flags)
|
||||
- [Feature Flags in CloudBees Enterprise On-Premise](#feature-flags-in-cloudbees-enterprise-on-premise)
|
||||
- [CloudBees Accelerator](#cloudbees-accelerator)
|
||||
- [Jervis: Jenkins as a service](#jervis-jenkins-as-a-service)
|
||||
- [Jenkins X](#jenkins-x)
|
||||
|
||||
@@ -270,12 +272,13 @@
|
||||
## Kubernetes Native Jenkins Operator
|
||||
* [github.com/jenkinsci/kubernetes-operator: 🌟](https://github.com/jenkinsci/kubernetes-operator) Kubernetes platform was released ten years after the first version of Hudson project. It means Jenkins couldn’t be designed to run on top of it. Jenkins Operator tries to bridge that gap.
|
||||
|
||||
## CloudBees Rollout and Feature Flags
|
||||
## CloudBees
|
||||
### CloudBees Rollout and Feature Flags
|
||||
* [CloudBees Rollout 🌟](https://app.rollout.io/)
|
||||
* [rollout.io: CloudBees Rollout Tutorial: Feature Flagging in your React Native App in 5 minutes](https://rollout.io/blog/rollout-tutorial-feature-flagging-in-your-react-native-app-in-5-minutes/)
|
||||
* [How to Disable Code: The Developer's Production Kill Switch 🌟](https://www.cloudbees.com/blog/how-disable-code-developers-production-kill-switch)
|
||||
|
||||
### Feature Flags in CloudBees Enterprise On-Premise
|
||||
#### Feature Flags in CloudBees Enterprise On-Premise
|
||||
* [CloudBees Releases Another Industry First: Feature Flagging for On-Premise Use 🌟](https://www.previous.cloudbees.com/press/cloudbees-releases-another-industry-first-feature-flagging-premise-use)
|
||||
* SAN JOSE, CA. – May 5, 2020 – CloudBees, Inc., the enterprise software delivery company, today announced a new release of CloudBees Feature Flags that enables developers to manage production deployments of new functionality in a controlled manner with an on-premise feature manager. The new offering strengthens CloudBees’ leadership in the continuous integration/continuous delivery (CI/CD) space by extending users’ ability to leverage feature flag technology in both on-premise and cloud environments. CloudBees Feature Flags is from the company and application formerly known as Rollout, [acquired last year by CloudBees](https://www.previous.cloudbees.com/press/cloudbees-acquires-rollout-adding-feature-flag-system).
|
||||
* Feature flags have emerged as popular tools for deploying new features with the added advantage of enabling risk-free experimentation and fast results. As organizations enhance applications with rich new capabilities, many use feature flags to preview features for select audiences, with the ability to pull them back quickly if the functionality is not successful. [In a recent survey](https://rollout.io/wp-content/uploads/2018/11/Rising.The_.Flag_.Rollout-1.pdf), 97% of respondents say that it is important for their organization to implement new application features quickly, yet 65% say it is difficult for their organization to do so safely. CloudBees Feature Flags enables developers to easily release new features with confidence, reduce risk in doing so and manage large numbers of feature flags at scale.
|
||||
@@ -283,6 +286,10 @@
|
||||
* CloudBees Feature Flags integrates with the company’s deep CI/CD capabilities, giving organizations the most comprehensive feature management capabilities in the software development life cycle (SDLC). The ability to use feature flagging in an on-premise environment also opens up new avenues for usage in industries, such as government, finance, pharmaceuticals, utilities and healthcare, where there can be a mix of on-premise and cloud environments.
|
||||
* “We recognize that many companies are realizing the benefits of feature flags,” said Moritz Plassnig, senior vice president and general manager, Software Delivery Management and Software Delivery Automation Cloud at CloudBees. “By flagging features, they no longer have to sacrifice innovation to lower risk. We felt that it was critical to offer this technology to any company working in on-premise or hybrid environments.”
|
||||
|
||||
### CloudBees Accelerator
|
||||
- [CloudBees Accelerator](https://www.cloudbees.com/products/accelerator/overview) Shorten Build and Test Times
|
||||
- [How to Speed Up Software Development with Build and Test Acceleration Tools](https://www.cloudbees.com/blog/how-speed-software-development-build-test-acceleration-tools)
|
||||
|
||||
## Jervis: Jenkins as a service
|
||||
* [Jervis](https://github.com/samrocketman/jervis/wiki) is [Sam Gleske](https://github.com/samrocketman)'s vision of a good way to roll out Jenkins as a service in very large organizations.
|
||||
* [SCM Filter Jervis YAML Plugin](https://plugins.jenkins.io/scm-filter-jervis/) This plugin is intended for Jenkins infrastructure relying on [jervis](https://github.com/samrocketman/jervis/wiki) to deliver software in a self-service manner. This plugin can also be used for Travis CI YAML.
|
||||
|
||||
@@ -14,6 +14,9 @@
|
||||
- [Kubectl Alternatives](#kubectl-alternatives)
|
||||
- [Manage Kubernetes (K8s) objects with Ansible Kubernetes Module](#manage-kubernetes-k8s-objects-with-ansible-kubernetes-module)
|
||||
- [Jenkins Kubernetes Plugins](#jenkins-kubernetes-plugins)
|
||||
- [Extending Kubernetes](#extending-kubernetes)
|
||||
- [Adding Custom Resources. Extending Kubernetes API with Kubernetes Resource Definitions. CRD vs Aggregated API](#adding-custom-resources-extending-kubernetes-api-with-kubernetes-resource-definitions-crd-vs-aggregated-api)
|
||||
- [Crossplane, a Universal Control Plane API for Cloud Computing. Crossplane Workloads Definitions](#crossplane-a-universal-control-plane-api-for-cloud-computing-crossplane-workloads-definitions)
|
||||
- [Client Libraries for Kubernetes](#client-libraries-for-kubernetes)
|
||||
- [Go Client for Kubernetes](#go-client-for-kubernetes)
|
||||
- [Fabric8 Java Client for Kubernetes](#fabric8-java-client-for-kubernetes)
|
||||
@@ -225,6 +228,29 @@ kubectl get secret <secret-name> --namespace=<source> -o yaml | sed ‘s/names
|
||||
* [Jenkins Kubernetes Plugin](https://plugins.jenkins.io/kubernetes/)
|
||||
* [Kubernetes Continuous Deploy](https://plugins.jenkins.io/kubernetes-cd/)
|
||||
|
||||
## Extending Kubernetes
|
||||
### Adding Custom Resources. Extending Kubernetes API with Kubernetes Resource Definitions. CRD vs Aggregated API
|
||||
- [Custom Resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
|
||||
- Use a custom resource (CRD or Aggregated API) if most of the following apply:
|
||||
- You want to use Kubernetes client libraries and CLIs to create and update the new resource.
|
||||
- You want top-level support from kubectl; for example, kubectl get my-object object-name.
|
||||
- You want to build new automation that watches for updates on the new object, and then CRUD other objects, or vice versa.
|
||||
- You want to write automation that handles updates to the object.
|
||||
- You want to use Kubernetes API conventions like .spec, .status, and .metadata.
|
||||
- You want the object to be an abstraction over a collection of controlled resources, or a summarization of other resources.
|
||||
- Kubernetes provides two ways to add custom resources to your cluster:
|
||||
- CRDs are simple and can be created without any programming.
|
||||
- API Aggregation requires programming, but allows more control over API behaviors like how data is stored and conversion between API versions.
|
||||
- Kubernetes provides these two options to meet the needs of different users, so that neither ease of use nor flexibility is compromised.
|
||||
- Aggregated APIs are subordinate API servers that sit behind the primary API server, which acts as a proxy. This arrangement is called API Aggregation (AA). To users, it simply appears that the Kubernetes API is extended.
|
||||
- CRDs allow users to create new types of resources without adding another API server. You do not need to understand API Aggregation to use CRDs.
|
||||
- Regardless of how they are installed, the new resources are referred to as Custom Resources to distinguish them from built-in Kubernetes resources (like pods).
|
||||
|
||||
### Crossplane, a Universal Control Plane API for Cloud Computing. Crossplane Workloads Definitions
|
||||
- [crossplane.io 🌟](https://crossplane.io/) Crossplane is an open source Kubernetes add-on that supercharges your Kubernetes clusters enabling you to provision and manage infrastructure, services, and applications from kubectl.
|
||||
- [Crossplane, a Universal Control Plane API for Cloud Computing](https://www.infoq.com/news/2019/01/upbound-crossplane/)
|
||||
- [Crossplane as an OpenShift Operator to manage and provision cloud-native services](https://blog.crossplane.io/crossplane-openshift-operator-cloud-native-services/)
|
||||
|
||||
## Client Libraries for Kubernetes
|
||||
### Go Client for Kubernetes
|
||||
- [Go client for Kubernetes](https://github.com/kubernetes/client-go) Go clients for talking to a kubernetes cluster.
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
- [Blogs](#blogs)
|
||||
- [CommandLineFu](#commandlinefu)
|
||||
- [Wait until Your Dockerized Database Is Ready before Continuing](#wait-until-your-dockerized-database-is-ready-before-continuing)
|
||||
- [Copr Build System](#copr-build-system)
|
||||
- [Linux Networking](#linux-networking)
|
||||
|
||||
## SSH
|
||||
@@ -79,6 +80,11 @@
|
||||
- [Wait until Your Dockerized Database Is Ready before Continuing](https://nickjanetakis.com/blog/wait-until-your-dockerized-database-is-ready-before-continuing) A zero dependency Bash script that waits until a command of your choosing has run successfully
|
||||
- [github.com/nickjj/wait-until](https://github.com/nickjj/wait-until)
|
||||
|
||||
### Copr Build System
|
||||
- Building a repo with RPM packages from PyPI is super easy using Copr.
|
||||
- [copr.fedorainfracloud.org](https://copr.fedorainfracloud.org/) Copr is an easy-to-use automatic build system providing a package repository as its output.
|
||||
- [Copr](https://pagure.io/copr/copr)
|
||||
|
||||
## Linux Networking
|
||||
- [ntop](http://www.ntop.org/)
|
||||
- [ngrep](http://ngrep.sourceforge.net/)
|
||||
|
||||
@@ -32,6 +32,7 @@
|
||||
- [Cluster Network Operator (CNO) & Routers](#cluster-network-operator-cno--routers)
|
||||
- [ServiceMesh Operator](#servicemesh-operator)
|
||||
- [Serverless Operator (Knative)](#serverless-operator-knative)
|
||||
- [Crossplane Operator (Universal Control Plane API for Cloud Computing)](#crossplane-operator-universal-control-plane-api-for-cloud-computing)
|
||||
- [Monitoring & Observability](#monitoring--observability)
|
||||
- [Grafana](#grafana)
|
||||
- [Prometheus](#prometheus)
|
||||
@@ -453,6 +454,9 @@ oc logs --namespace=openshift-ingress-operator deployments/ingress-operator
|
||||
- [openshift.com/learn/topics/serverless](https://www.openshift.com/learn/topics/serverless)
|
||||
- [redhat-developer-demos.github.io/knative-tutorial](https://redhat-developer-demos.github.io/knative-tutorial)
|
||||
|
||||
##### Crossplane Operator (Universal Control Plane API for Cloud Computing)
|
||||
- [Crossplane as an OpenShift Operator to manage and provision cloud-native services](https://blog.crossplane.io/crossplane-openshift-operator-cloud-native-services/)
|
||||
|
||||
#### Monitoring & Observability
|
||||
##### Grafana
|
||||
- Integrated Grafana v5.4.3 (deployed by default):
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Test Automation with Postman
|
||||
# Test Automation with Postman. API Testing
|
||||
- [getpostman.com](https://www.getpostman.com/)
|
||||
- [blog.getpostman.com](https://blog.getpostman.com/)
|
||||
- [Dzone: getting started with postman](https://dzone.com/articles/getting-started-with-postman)
|
||||
@@ -7,3 +7,11 @@
|
||||
- [Dzone: how to use postman to manage and execute your APIs](https://dzone.com/articles/how-to-use-postman-to-manage-and-execute-your-apis)
|
||||
- [Dzone: how to download and install postman REST client](https://dzone.com/articles/how-to-download-and-install-postman-rest-client-so)
|
||||
- [Dzone: using postman REST client, quick tips](https://dzone.com/articles/using-postman-rest-client-cleverly-some-quick-tips)
|
||||
|
||||
## Newman
|
||||
- [Newman](https://github.com/postmanlabs/newman) is a command-line collection runner for Postman
|
||||
- [Automated API testing for the KIE Server 🌟](https://developers.redhat.com/blog/2020/05/01/automated-api-testing-for-the-kie-server/)
|
||||
|
||||
## Drools
|
||||
- [Drools](https://www.drools.org/)
|
||||
- [KIE Server](https://registry.hub.docker.com/r/jboss/kie-server/)
|
||||
@@ -27,6 +27,7 @@
|
||||
* [Deploying and Managing a Minimal App in a Kubernetes Cluster with Terraform and Ansible](https://www.hashicorp.com/resources/deploying-managing-minimal-app-kubernetes-cluster-terraform-ansible/)
|
||||
* [Deploy Any Resource With The New Kubernetes Provider for HashiCorp Terraform](https://www.hashicorp.com/blog/deploy-any-resource-with-the-new-kubernetes-provider-for-hashicorp-terraform/)
|
||||
* [Testing Infrastructure as Code on Localhost](https://www.hashicorp.com/resources/testing-infrastructure-as-code-on-localhost/)
|
||||
* [Why we use Terraform and not Chef, Puppet, Ansible, SaltStack, or CloudFormation](https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c)
|
||||
|
||||
### Awesome Terraform
|
||||
* [github.com/shuaibiyy/awesome-terraform](https://github.com/shuaibiyy/awesome-terraform)
|
||||
|
||||
Reference in New Issue
Block a user