vfarcic

# Source: https://gist.github.com/8ef7f6cb24001e240432cd6a82a515fd

####################
# Create a Cluster #
####################

# Only if you did not yet clone that repository
git clone \
    https://github.com/vfarcic/devops-catalog-code.git

vfarcic

# Source: https://gist.github.com/ebe4ad31d756b009b2e6544218c712e4

####################
# Create a Cluster #
####################

# Only if you did not yet clone that repository
git clone \
    https://github.com/vfarcic/devops-catalog-code.git

vfarcic

####################
# Create a Cluster #
####################

# Make sure that Kubernetes is enabled

# Tested with 4 CPUs and 5GB RAM

#######################
# Destroy The Cluster #

vfarcic

####################
# Create a Cluster #
####################

minikube start --memory 5g --cpus 4

#######################
# Destroy The Cluster #
#######################

vfarcic

DEmystifying High-Availability

What Is High-Availability?

Availability is the period of time when a service (an application or a system) is available. It is measured from user's perspective and, in this context, a user is anyone or anything interacting with that service. It's a simple question. Is the application available to users (almost) always?

Lack of availability can be caused by many things. The application might not be running for a while because it failed or it is being upgraded. Often, an application might be up-and-running, but not available to users. It might be saturated with too many requests, dependant applications might not be available, networking might not be working, and so on and so forth.

High-availability means that an application is available almost always. Today, highly-available applications are considered those that have at least a few nines after 99%. Anything below at least one nine after the decimal (99.9%), is NOT considered highly available by today's standards. That m

vfarcic

# Source: https://gist.github.com/6d6041896ef1243233c11b51d082eb6e

# Pre-requisites: https://gist.github.com/34009f4c65683dd3a82081fa8d76cd85

az acr login --name $REGISTRY_NAME

docker image pull \
    vfarcic/devops-toolkit-series

export IMAGE=$REGISTRY_NAME.azurecr.io/devops-toolkit-series:0.0.1

vfarcic

# Source: https://gist.github.com/2ef4e1933d7c46fb1ddc41a633e1e7c7

# Pre-requisites: https://gist.github.com/fa047ab7bb34fdd185a678190798ef47

git clone \
    https://github.com/vfarcic/devops-catalog-code.git

cd devops-catalog-code

git pull

vfarcic

# Source: https://gist.github.com/59f647c62db7502a2ad9e21210f38c63

# Pre-requisites: https://gist.github.com/2aa8ee4a6451fd762b1a10799bbeac88

gcloud auth configure-docker

docker image pull \
    vfarcic/devops-toolkit-series

export IMAGE=gcr.io/$PROJECT_ID/devops-toolkit-series:0.0.1

vfarcic

# Source: https://gist.github.com/2aa8ee4a6451fd762b1a10799bbeac88

##########
# Create #
##########

# Only if you did not yet clone that repository
git clone \
    https://github.com/vfarcic/devops-catalog-code.git

vfarcic

######################
# Creating A Cluster #
######################

minikube start \
    --vm-driver virtualbox \
    --cpus 4 \
    --memory 8192

minikube addons enable default-storageclass