bobbybabu007 Goto Github PK

firstrepo

fleetman-api-gateway

front-end

Front-end application for ALL the microservices

gcp-deploystack-nosql-client-server

gha-python-django-image-generator-app

gha-python-image-app

python app for build pipelines

git-workshop

Git for DevOps

github-actions-runner

gitops-simple-app

gke-cluster-provision-terraform

gke-microservices-1-online-boutique-using-manifests

Sample cloud-native application with 10 microservices showcasing Kubernetes, Istio, gRPC and OpenCensus.

gke-microservices-2-robot-shop-using-helm-charts

Sample microservices application for playing with

gke-python-flask-sample-application

Hello world Python Flask application Dockerized

golangsample

Sample Golang code for build Docker images, publish then and use on Cloud Native experiments.

gradle-pipeline

guide-cloud-google

A guide on how to deploy microservices to Google Kubernetes Engine (GKE) on Google Cloud Platform (GCP).

hkoscon2020

Repo for my GH Actions sessions at the Hong Kong Opensource Conference 2020

istio-workshop-labs

Istio Wokshop Labs

jdk-mvn-py3

OpenJDK Java 8/11 + Maven 3.6 + Python 3.8 + pip 20.0 + node 14 + npm 6 + Gradle 6

jenkins-custom-2-casc

Repository for our casc demo setup

jenkins-docker-k8s

Deploying and Scaling Jenkins on Kubernetes

jenkins-exercise-nodejs-pipeline

jenkins-first-build-project

jenkins-libraries

jenkins-pipeline-demos

jenkins-pipeline-examples

jenkins-python-pipeline

jenkinsecs

We want to make a scalable , recoverable Jenkins build cluster which does its capacity planning according to the scalability rule that we define during creation. What it means is we are trying to make a build pipeline which does its own capacity planning, will take minimum manual effort to setup/recover and is leveraging the cloud services of AWS. There are 2 ways to go about it, as suggested in the AWS White paper linked in the reference section. First, the traditional deployment on top of Amazon Elastic Compute Cloud (Amazon EC2) barebone machines. This approach is just like installing Jenkins on a local server, it comes with the traditional pros and cons. The second is the containerized deployment that leverages Amazon EC2 Container Service (Amazon ECS). Using an extensive plugin system, Jenkins offers options for integrating with many AWS services and can morph to fit most use cases (e.g., traditional development pipelines, mobile development, security requirements, etc.). While the white paper suggests using EFS in a containerized system, we are going to work around it because of the region we are in (ca-central-1)

jenkinsfiles

Examples for jenkins pipelines, comparing scripted and declarative syntax

k8s-aks-101-workshop

AKS 101