All Projects → shalb →

shalb /

Licence: apache-2.0
Kubernetes-based Dev Environments with GitOps

Programming Languages

31211 projects - #10 most used programming language

Projects that are alternatives of or similar to

Security scanner for your Terraform code
Stars: ✭ 3,622 (+2868.85%)
Mutual labels:  aws, hacktoberfest, terraform, infrastructure-as-code, digitalocean
Prevent cloud misconfigurations during build-time for Terraform, Cloudformation, Kubernetes, Serverless framework and other infrastructure-as-code-languages with Checkov by Bridgecrew.
Stars: ✭ 3,572 (+2827.87%)
Mutual labels:  aws, hacktoberfest, terraform, infrastructure-as-code
Iam Policy Json To Terraform
Small tool to convert an IAM Policy in JSON format into a Terraform aws_iam_policy_document
Stars: ✭ 282 (+131.15%)
Mutual labels:  aws, hacktoberfest, terraform, infrastructure-as-code
Terraform Provider Digitalocean
Terraform DigitalOcean provider
Stars: ✭ 296 (+142.62%)
Mutual labels:  digitalocean, hacktoberfest, terraform, infrastructure-as-code
Aws Cdk
The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
Stars: ✭ 7,963 (+6427.05%)
Mutual labels:  aws, hacktoberfest, infrastructure-as-code
🚀 Geodesic is a DevOps Linux Distro. We use it as a cloud automation shell. It's the fastest way to get up and running with a rock solid Open Source toolchain. ★ this repo!
Stars: ✭ 629 (+415.57%)
Mutual labels:  aws, terraform, infrastructure-as-code
Terraform Modules
Terraform Modules
Stars: ✭ 25 (-79.51%)
Mutual labels:  aws, terraform, infrastructure-as-code
A Terraform module to create and maintain Kubernetes clusters on AWS easily, relying entirely on kops
Stars: ✭ 38 (-68.85%)
Mutual labels:  aws, terraform, infrastructure-as-code
Terratag is a CLI tool that enables users of Terraform to automatically create and maintain tags across their entire set of AWS, Azure, and GCP resources
Stars: ✭ 385 (+215.57%)
Mutual labels:  aws, terraform, infrastructure-as-code
Terraform Sqs Lambda Trigger Example
Example on how to create a AWS Lambda triggered by SQS in Terraform
Stars: ✭ 31 (-74.59%)
Mutual labels:  aws, terraform, infrastructure-as-code
Minimal and free Kubernetes distribution with Terraform
Stars: ✭ 1,397 (+1045.08%)
Mutual labels:  aws, digitalocean, terraform
A collection of bash shell scripts for automating various tasks with Amazon Web Services using the AWS CLI and jq.
Stars: ✭ 493 (+304.1%)
Mutual labels:  aws, terraform, infrastructure-as-code
CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
Stars: ✭ 6,316 (+5077.05%)
Mutual labels:  aws, terraform, infrastructure-as-code
A Table of Contents of all Gruntwork Code
Stars: ✭ 111 (-9.02%)
Mutual labels:  aws, terraform, infrastructure-as-code
Reads from existing Cloud Providers (reverse Terraform) and generates your infrastructure as code on Terraform configuration
Stars: ✭ 452 (+270.49%)
Mutual labels:  aws, terraform, infrastructure-as-code
Displays CI statuses on a dashboard and triggers fun modules representing the status!
Stars: ✭ 34 (-72.13%)
Mutual labels:  hacktoberfest, continuous-deployment, gitlab
Terraform Security Scan
Run a security scan on your terraform with the very nice
Stars: ✭ 64 (-47.54%)
Mutual labels:  aws, hacktoberfest, terraform
Terraform Aws Asg
Terraform AWS Auto Scaling Stack
Stars: ✭ 58 (-52.46%)
Mutual labels:  aws, terraform, infrastructure-as-code
Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.
Stars: ✭ 2,687 (+2102.46%)
Mutual labels:  aws, terraform, infrastructure-as-code
Terraform Aws Gitlab Runner
Terraform module for AWS GitLab runners on ec2 (spot) instances
Stars: ✭ 292 (+139.34%)
Mutual labels:  aws, terraform, infrastructure-as-code - Kubernetes-based Dev Environment in Minutes

follow on Twitter follow on Facebook is an open-source system delivered as GitHub Action or Docker Image for creating and managing Kubernetes clusters with simple manifests by GitOps approach.

Designed for developers that don't want waste time to configure Kubernetes stuff and just need: kubeconfig, dashboard, logging, monitoring and deployment systems out-of-the-box.

GitOps infrastructure management with Terraform and continuous deployment with ArgoCD. Easily extendable by pre-configured applications and modules. Quick integration with Jenkins, GitLab or other CI/CD systems. Supports multiple Cloud Providers and Kubernetes versions.


Principle diagram

Small and understandable yaml definition:

  installed: true
  name: develop
    provider: aws
    region: eu-central-1
    vpc: default
      type: minikube
      instanceType: m5.large
    nginx-ingress: true
    cert-manager: true
    - /kubernetes/apps/samples turns it into powerful infrastructure as a code! diagram

How it works

In the background:

  • Terraform creates a "state bucket" in your Cloud Provider account where all infrastructure objects will be stored. Typically it is defined on Cloud Object Storage like AWS S3.
  • Terraform modules create Minikube/EKS/GKE/etc.. cluster, VPC and DNS zone within your Cloud Provider.
  • ArgoCD Continuous Deployment system is deployed inside Kubernetes cluster. It enables you to deploy your ArgoCD Applications from raw manifests, helm charts or kustomize yaml's.
  • GitHub CI runner is deployed into your Kubernetes cluster and is used for your apps building CI pipelines with GitHub Actions.

You receive:

  • Automatically generated kubeconfig, ssh-access, and ArgoCD UI URLs
  • Configured: Ingress Load Balancers, Kubernetes Dashboard, Logging(ELK), Monitoring(Prometheus/Grafana)


Quick Start

normally it takes 15 minutes

  1. Create a separate repository for the infrastructure code that will be managed by cluster.devin GitHub. This repo will host code for your clusters, deployments, applications and other resources. Clone the repo locally:

    git clone

Next steps should be done inside that repo.

Expand steps for specific for Amazon AWS
  1. Create a new AWS user with limited access in IAM. Watch video example to create the user and apply policy. If you need more information about AWS users - please check aws documentation for details.

    Resulting access pair should look like:

    AWS_SECRET_ACCESS_KEY = SuperAwsSecret
  2. Add credentials to you repo Secrets under GitHub's repo setting Settings → Secrets, the path should look like

    GitHub Secrets

  3. In your repo, create a Github workflow file: .github/workflows/main.yml and example manifest: with the cluster definition.

    Or download example files to your local repo clone using the next commands:

    # Sample with Minikube cluster
    export RELEASE=v0.3.3
    mkdir -p .github/workflows/ && wget -O .github/workflows/main.yml "${RELEASE}/.github/workflows/aws.yml"
    mkdir -p && wget -O "${RELEASE}/"
  4. In the cluster manifest ( you can set your own Route53 DNS zone. If you don't have any hosted public zone you can set just domain: and we will create it for you. Or you can create it manually with instructions from AWS Website.

Expand steps for specific for DigitalOcean
  1. Login to your DO account. You can create a default VPC inside your account if you wish: Manage->Networking->VPC-Create VPC Network.

  2. You need to generate DO API Token and DO Spaces keys. To generate API Token please consult DO document. It should like:

    DIGITALOCEAN_TOKEN: "83e209a810b6c1da8919fe7265b9493992929b9221444449"

    To generate DO Spaces secrets please consult DO document Resulting Key and Secret should look like:

    SPACES_SECRET_ACCESS_KEY: "njVtezJ7t2ce1nlohIFwoPHHF333mmcc2"

    Add TOKEN and SPACES keys to your repo secrets or env variables. In GitHub: Settings → Secrets, the path should look like:

  3. In your repo, create a Github workflow file: .github/workflows/main.yml and example manifest: with the cluster definition.

    Or download example files to your local repo clone using the next commands:

    # Sample with DO Managed Kubernetes Cluster
    export RELEASE=v0.3.3
    mkdir -p .github/workflows/ && wget -O .github/workflows/main.yml "${RELEASE}/.github/workflows/digitalocean.yml"
    mkdir -p && wget -O "${RELEASE}/"
  4. In the cluster manifest ( you can set your own Domain Zone. If you don't have any hosted public zone you can set just domain: and we will create it for you. Or you can create it manually and add to your account with instructions from DO website.

  1. You can change all other parameters or leave default values in the cluster manifest. Leave the Github workflow file .github/workflows/main.yml as is.

  2. Copy sample ArgoCD Applications from /kubernetes/apps/samples and Helm chart samples from /kubernetes/charts/wordpress to the same paths into your repo.

    Or download application samples directly to local repo clone with commands:

    export RELEASE=v0.3.3
    # Create directory and place ArgoCD applications inside
    mkdir -p kubernetes/apps/samples && wget -O kubernetes/apps/samples/helm-all-in-app.yaml "${RELEASE}/kubernetes/apps/samples/helm-all-in-app.yaml"
    wget -O kubernetes/apps/samples/helm-dependency.yaml "${RELEASE}/kubernetes/apps/samples/helm-dependency.yaml"
    wget -O kubernetes/apps/samples/raw-manifest.yaml "${RELEASE}/kubernetes/apps/samples/raw-manifest.yaml"
    # Download sample chart which with own values.yaml
    mkdir -p kubernetes/charts/wordpress && wget -O kubernetes/charts/wordpress/Chart.yaml "${RELEASE}/kubernetes/charts/wordpress/Chart.yaml"
    wget -O kubernetes/charts/wordpress/requirements.yaml "${RELEASE}/kubernetes/charts/wordpress/requirements.yaml"
    wget -O kubernetes/charts/wordpress/values.yaml "${RELEASE}/kubernetes/charts/wordpress/values.yaml"

    Define path to ArgoCD apps in the cluster manifest:

        - /kubernetes/apps/samples
  3. Commit and Push files to your repo.

  4. Set the cluster to installed: true, commit, push and follow the Github Action execution status, the path should look like In the GitHub action output you'll receive access instructions to your cluster and services: GHA_GetCredentials

  5. Voilà! You receive GitOps managed infrastructure in code. So now you can deploy applications, create more clusters, integrate with CI systems, experiment with the new features and everything else from Git without leaving your IDE.


To shutdown the cluster and remove all associated resources:

  1. Open directory in your repo.
  2. In each manifest set cluster.installed to false
  3. Commit and push changes
  4. Open Github Action output to see the removal status

After successful removal, you can safely delete cluster manifest file from directory.

Technical diagram technical diagram


The project is in Alpha Stage. Roadmap details: docs/


If you want to spread the project with your own code, you could start contributing with this quick guide: docs/


Code of Conduct and License

Code of Conduct described in

Product licensed under Apache 2.0.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].