ACE the hard way!
Download and install the following tools:
- Git (GitBash if you are on Windows)
Run the following command to verify that git is working:
git --version
Run the following command to login in using you @evry.com account:
az login
az account set -s f18e2af9-2f65-4e18-bc39-54d74e271e7c
Run the following command to verify that kubectl is working:
kubectl version
NB! Make sure you have at least version
v0.12.6installed.
terraform --version
- Create a new local git repository on your machine (
git init) - Add the following to your
.gitignorefile:
.env
.terraform
*.tfstate*
- Commit your
.gitignorefile (git add .gitignore; git commit) - Add your assigned remote (
git remote add origin master git@github.com...) - Push your branch to the remote (
git push -u origin master)
Move the .conf file you have recieved to the git repository and rename it to
.env. You can source the file by running the following command:
source .env
Pro tip! Add the terraform syntax highlighter for your favorite editor!
NB! In order to complete this lab you will need a .env file with your
assigned Azure credentials! If you have not yet got it, please ask your
instructor.
In order to get started with Terraform we need the following parts:
- One or more Terraform providers. For this workshop we will be
using the
azurermprovider. - A remote state backend for storing the Terraform state.
- Resources (the items) that Terraform should set up.
Terraform is very relax when it comes to file structure. It dosn't require any main methods or file conventions as it creates a depencendy graph dynamically. However it requires all files to be at the root folder (unless you are using modules).
Start by create a folder named terraform in your git repo; inside this the
following files should be present. Just create empty files and we'll fill them
with content as we go.
variables.tfprovider.tfmain.tf
This file will hold our Terraform variables. As the name suggests these can be re-used accross the Terraform setup and they can have different values for different environments.
All variables needs to be declared and we recommend that you put them in this file in order to keep track of them an better re-usability.
NB! Terraform favours underscore
_when seperating words in variables like this:my_awesome_variable. Try to adheare to this to make the code more uniform.
Variables are declared like this:
variable "my_variable" {}This will create an unitialized variable which means that you need to assign it a value at runtime in order for Terraform to procede.
If you want to hava a default value you can do it like this:
value "my_variable" {
default = "This is a default value"
}Variables are strings by default but Terraform supports a variety of other data types.
Go ahead and add the following variables to your variables.tf file now:
variable "user_id" {}
variable "azure_location" {}
variable "azure_resource_group" {}
variable "azure_client_id" {}
variable "azure_client_secret" {}
variable "azure_tenant_id" {}
variable "azure_subscription_id" {}As you can see they have no default value. That is becuase we never want to hard code credentials or other sensitive information inside our configuration, these should be kept secret and injected using environment variables.
As mentioned we will be using the azurerm Terrafrom provider for
this workshop. The provider configuration connects to the infrastructure and
makes it possible for Terraform to set up, modify and delete resources on your
behalf.
The provider defintion looks like this:
provider "azurerm" {
subscription_id = "${var.azure_subscription_id}"
client_id = "${var.azure_client_id}"
client_secret = "${var.azure_client_secret}"
tenant_id = "${var.azure_tenant_id}"
version = "v1.33.0"
skip_provider_registration = true
}In order for Terraform to remember what had already been set up you need to set
up the remote state backend. This is using a storage account on Azure and it is
defined like this in the provider.tf file:
terraform {
backend "azurerm" {
container_name = "terraform-state"
key = "terraform.tfstate"
}
}
Once all of this is set up you can initiate Terraform using the following command:
terraform init -reconfigure \
-backend-config="access_key=$TF_VAR_storage_access_key" \
-backend-config="storage_account_name=$TF_VAR_storage_account_name"NB! If this command fails, be sure you have run
source .env
As you can see this corresponds to the variables we have set up on our
variables.tf file.
Now let's add something to our main.tf file so we can verify that our setup is
working.
data "azurerm_resource_group" "ws" {
name = var.azure_resource_group
}This won't actually create something, this is a Terraform data source definition which is a reference to an existing resource.
Once you have this working you can verify your setup by running the following commands:
terraform fmt
terraform verify
In order to actually run this and see what it does you can run the following commands:
terraform plan
terraform apply
This should give an output like this:
...
See main.tf for how to set up AKS and ACR.
In order to get the credentials run the following command:
az aks get-credentials \
--resource-group $TF_VAR_azure_resource_group \
--name aks-ace \
--file - > ~/.kube/config
If you get any problems try the following:
- Make sure you have sourced your
.envfile (source .env)
Now you can list all the pods in your cluster by running the following command:
kubectl get pods --all-namespaces
resource "helm_release" "traefik" {
name = "traefik"
namespace = "kube-system"
repository = "${data.helm_repository.stable.metadata.0.name}"
chart = "traefik"
version = "1.76.1"
values = [<<EOF
...
EOF
]
}
While this is deploying run the following commands in order to follow the progress:
kubectl get pods --all-namespaces --watch
This lab your will learn to build and deploy a simple, multi-tier web application using Kubernetes and Docker. This example consists of the following components:
-
A single-instance Redis master to store guestbook entries
-
Multiple replicated Redis instances to serve reads
-
Multiple web frontend instances
-
https://kubernetes.io/docs/tutorials/stateless-application/guestbook/
Now, create an ingress configrutaion for your guest book such that you can visit it over the DNS and Ingress Controller that we have set up in previous labs.
The DNS name for the ingress configuration is found in your .env file. Add a
prefix like guestbook. to your $TF_VAR_aks_ingress_dns_name variable.
Now we can create a Helm Chart for our guestbook application in order to get it deployed via our Terraform setup.
Run the following command to create a new Helm Chart from the root of your git repository:
helm create guestbook-chart
This creates a new directory explore what is in it before moving on. You now
need to take the Kubernetes configuration files and add them to the
./templates directory.
Run the following command to install the new Helm Chart:
helm install \
--set ingress.hostName=guestbook.<YOU ID HERE>.workshop-2019.ace.evry.services \
--name guestbook \
./guestbook-chart
TBA
TBA
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.11.0/crds.yaml
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.11.0/olm.yaml
kubectl apply -f manifests/prometheus-operator.yaml
kubectl apply -f manifests/prometheus-cr.yaml
kubectl apply -f manifests/grafana-operator.yaml
kubectl apply -f manifests/grafana-cr.yaml
kubectl apply -f manifests/grafana-default-dashboards.yaml
TBA