From b86fb1a8da5d019816343bb5b1fe82a32cf2d8e2 Mon Sep 17 00:00:00 2001 From: Sam Bukowski Date: Thu, 19 Oct 2023 15:57:36 -0600 Subject: [PATCH] fix bare urls --- .../cloud-rollup-deployment/1-digital-ocean.md | 6 +++--- docs/dusknet/cloud-rollup-deployment/2-gcp.md | 14 +++++++------- docs/dusknet/cloud-rollup-deployment/3-azure.md | 12 +++++++----- docs/dusknet/cloud-rollup-deployment/4-aws.md | 10 +++++----- 4 files changed, 22 insertions(+), 20 deletions(-) diff --git a/docs/dusknet/cloud-rollup-deployment/1-digital-ocean.md b/docs/dusknet/cloud-rollup-deployment/1-digital-ocean.md index 0b04b953..2bded895 100644 --- a/docs/dusknet/cloud-rollup-deployment/1-digital-ocean.md +++ b/docs/dusknet/cloud-rollup-deployment/1-digital-ocean.md @@ -22,7 +22,7 @@ You must use at least a 2 node cluster. ## Setup Digital Ocean Ingress We use the Ingress NGINX Controller for consistency across deployment environments: -- https://kubernetes.github.io/ingress-nginx/deploy/#digital-ocean +- ```bash kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/do/deploy.yaml @@ -35,7 +35,7 @@ You must configure a DNS record because our ingress configuration uses name base ::: Follow the instructions here: -- https://docs.digitalocean.com/products/networking/dns/getting-started/dns-registrars/ +- - This is where you will set `` @@ -61,7 +61,7 @@ ingress-nginx-controller-admission ClusterIP 10.245.106.99 ## Set up an `A` Record for your Load Balancer Follow the steps here to set up an `A` record for DNS: -- https://docs.digitalocean.com/products/networking/dns/how-to/manage-records/#a-records +- :::tip When configuring the `A` record for DNS, the `directs to` value should specify the `loadbalancer` which was created by the `nginx-ingress-controller`. diff --git a/docs/dusknet/cloud-rollup-deployment/2-gcp.md b/docs/dusknet/cloud-rollup-deployment/2-gcp.md index ea267926..3d322266 100644 --- a/docs/dusknet/cloud-rollup-deployment/2-gcp.md +++ b/docs/dusknet/cloud-rollup-deployment/2-gcp.md @@ -12,16 +12,16 @@ The list of local dependencies for the following instructions [can be found here ## Create a GCP (Google) Account -Follow instructions here: https://console.cloud.google.com/ +Follow instructions here: ## Install GCP `gcloud` CLI -Find the correct cli for your OS here: https://cloud.google.com/sdk/docs/install +Find the correct cli for your OS here: ## Create a Google Cloud Project See the full instructions here: -- https://cloud.google.com/resource-manager/docs/creating-managing-projects +- We recommend using the cli commands, which can be found on the above page by selecting the `gcloud` tabs within the instructions: @@ -39,7 +39,7 @@ gcloud config set project PROJECT_ID ## Enable Billing See the following page for setting up a billing account that suits your needs: -- https://cloud.google.com/billing/docs/how-to/verify-billing-enabled#console +- ## Enable GKE API @@ -50,7 +50,7 @@ gcloud services enable container.googleapis.com ## GKE Quickstart Follow the Quickstart guide to create your GKE cluster: -- https://cloud.google.com/kubernetes-engine/docs/deploy-app-cluster +- ### Create a GKE Cluster @@ -80,7 +80,7 @@ gcloud container clusters get-credentials hello-cluster \ ## Deploy Ingress Nginx Controller See the Kubernetes GCE-GKE nginx installation guid here: -- https://kubernetes.github.io/ingress-nginx/deploy/#gce-gke +- ```bash kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/cloud/deploy.yaml @@ -121,7 +121,7 @@ Creating an `A` record will depend on where you purchased your domain from. Each domain provider will have different steps required to set up an A record. An example (for Google domains) can be seen here: -- https://support.google.com/a/answer/2579934?hl=en +- :::danger You must configure a DNS record because our ingress configuration uses name diff --git a/docs/dusknet/cloud-rollup-deployment/3-azure.md b/docs/dusknet/cloud-rollup-deployment/3-azure.md index 91f90192..a5854450 100644 --- a/docs/dusknet/cloud-rollup-deployment/3-azure.md +++ b/docs/dusknet/cloud-rollup-deployment/3-azure.md @@ -12,16 +12,18 @@ The list of local dependencies for the following instructions [can be found here ## Create an Azure Account -https://azure.microsoft.com/en-us/free +Create your account here: +- ## Install Azure `az` CLI Following the instructions on how to install the cli for your OS here: -- https://learn.microsoft.com/en-us/cli/azure/install-azure-cli +- ## AKS Quickstart -https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-cli +See the quickstart guide here: +- ### Prerequisites @@ -57,7 +59,7 @@ az aks get-credentials --resource-group myResourceGroup --name myAKSCluster ### Deploy Nginx Ingress Controller -https://kubernetes.github.io/ingress-nginx/deploy/#azure + ```bash kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/cloud/deploy.yaml @@ -99,7 +101,7 @@ Creating an `A` record will depend on where you purchased your domain from. Each domain provider will have different steps required to set up an A record. An example (for Google domains) can be seen here: -- https://support.google.com/a/answer/2579934?hl=en +- :::danger You must configure a DNS record because our ingress configuration uses name diff --git a/docs/dusknet/cloud-rollup-deployment/4-aws.md b/docs/dusknet/cloud-rollup-deployment/4-aws.md index ae62b274..cb81bc09 100644 --- a/docs/dusknet/cloud-rollup-deployment/4-aws.md +++ b/docs/dusknet/cloud-rollup-deployment/4-aws.md @@ -14,24 +14,24 @@ The list of local dependencies for the following instructions [can be found here ## Create an AWS Account -https://portal.aws.amazon.com/gp/aws/developer/registration/index.html + ## Install `aws` CLI Installation links for your OS can be found here: -- https://aws.amazon.com/cli/ +- ## Create an Access Key To create an access key, follow the instructions here: -- https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html +- :::danger This doesn’t follow best security practices, do not do this on an important AWS account which has production resources on it. ::: -Go to IAM section of console: https://console.aws.amazon.com/iam/ +Go to IAM section of console: Create an access key for your `root` user. @@ -50,7 +50,7 @@ Default output format [None]: # Create Amazon EKS Cluster -https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html + ```bash aws cloudformation create-stack \