Skip to content

Latest commit

 

History

History
87 lines (57 loc) · 4.03 KB

README.md

File metadata and controls

87 lines (57 loc) · 4.03 KB
Raw

DevOps Lab

Build environment

This is the main repo I use to test Kubernetes / DevOps applications, products, and processes. It's essentially my playground in Azure.

I started off with a Kubernetes cluster, Nexus Repository OSS, and Velero for backups, but there are loads more being used now.

Contents

Getting Started

Follow the sections below to prepare and configure your environment, ready to run your first build:

Prereqs

DNS zones and TLS certs are typically created out-of-band (outside of the main build automation), so we'll create these only once, and they will exist across multiple builds.

Configure DNS Zone

Use the Setting up ExternalDNS for Services on Azure tutorial to create and configure your DNS zone, as we will be using ExternalDNS within the kubernetes cluster to dynamically update DNS records.

Configure Key Vault / LetsEncrypt TLS Certificate

Use the keyvault-acmebot Getting Started guide to deploy AcmeBot and configure a wildcard certificate for your domain (eg: *.domain.com).

Configure Azure Authentication

Before the build GitHub Action workflow can be run, authentication needs to be configured for Azure.

  1. Create a Service Principal with a Client Secret.

  2. Grant permissions to manage Azure Active Directory.

Create Secrets

TODO: Update this for OIDC auth (federated credential): https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_oidc#configuring-the-service-principal-in-terraform

Once Azure authentication has been configured, the Service Principle credential values can be passed as environment variables.

Use these instructions to create the following secrets for your repository:

  • ARM_CLIENT_ID
  • ARM_SUBSCRIPTION_ID
  • ARM_TENANT_ID

Update the Workflow Environment Variables

TODO - update key vault and dns env vars.

Running the Build Workflow

Now that Azure authentication has been configured with corresponding secrets, the build workflow is ready to be run:

  1. Navigate to the build workflow.
  2. Click the Run workflow drop-down button.
  3. Select the desired branch.
  4. Click the Run workflow button.

Running the Destroy Workflow

There will be ongoing costs if the environment is left running, so to avoid unexpected bills the destroy workflow should be run once testing has been completed:

  1. Navigate to the destroy workflow.
  2. Click the Run workflow drop-down button.
  3. Select the desired branch.
  4. Click the Run workflow button.