Skip to content

Latest commit

 

History

History
144 lines (110 loc) · 4.65 KB

README.md

File metadata and controls

144 lines (110 loc) · 4.65 KB
Raw

Deno Cluster AWS module

Prerequisites

  1. Make sure you have to following command line tools installed:
    • aws (AWS CLI)
    • kubectl (Kubernetes command line tool)
    • helm (Helm CLI)
  2. Log in to AWS with aws configure or aws sso login.

Provision AWS resources using terraform

Fill out the locals block with information specific to your environment.

You'll need designate domain name like mycluster.deno-cluster.net or dev.mycompany.com, which you can delegate (using an NS record) to AWS hosted zone, to attach to the cluster.

locals {
  domain_name          = "mycluster.deno-cluster.net" # <— The DNS zone that terraform will create in AWS.
  eks_cluster_name     = "deno-cluster-01"            # <— The name of the EKS cluster.
  eks_cluster_region   = "us-west-2"                  # <— The AWS region to deploy to.
}

Finally, run terraform init to initialize the Terraform configuration and run terraform apply to create the resources.

Take note of the outputs of the plan, you'll need these values later to configure your Deno Cluster installation.

DNS Configuration

In your domain registrar or DNS provider, delegate the DNS zone for your cluster domain name (e.g. mycluster.deno-cluster.net) to AWS. Use the following command to get the NS records for the DNS zone (set DOMAIN_NAME to your domain name):

terraform output

The name servers will look similar to this:

# ...
hosted_zone_nameservers = tolist([
  "ns-1441.awsdns-52.org",
  "ns-1909.awsdns-46.co.uk",
  "ns-429.awsdns-53.com",
  "ns-592.awsdns-10.net",
])
# ...

To delegate your cluster domain name to AWS DNS, you would add the following records to your existing DNS provider:

mycluster.deno-cluster.net.  IN  NS  ns-1.awsdns-05.org.
mycluster.deno-cluster.net.  IN  NS  ns-2.awsdns-50.net.
mycluster.deno-cluster.net.  IN  NS  ns-3.awsdns-22.com.
mycluster.deno-cluster.net.  IN  NS  ns-4.awsdns-08.co.uk.

Note

Once the Terraform plan has run to completion, the AWS will validate the certificate through the DNS records that were created by Terraform. You don't have to wait for it to be validated to continue, but you will need to make sure the validation completed before making a deployment. To do so, run the following command:

aws acm wait certificate-validated --certificate-arn <arn>

Connect To The Cluster

Update DENO_CLUSTER_NAME and DENO_CLUSTER_REGION with your values and run:

export DENO_CLUSTER_NAME=deno-cluster-01
export DENO_CLUSTER_REGION=us-west-2
aws eks update-kubeconfig --name $DENO_CLUSTER_NAME --region $DENO_CLUSTER_REGION

Install Dependencies In The Cluster

The Deno Cluster Helm chart depends on karpenter, cert-manager, and opentelemetry-operator. You can install them with the following commands:

helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts --force-update
helm repo add jetstack https://charts.jetstack.io --force-update

helm install \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.15.3 \
  --set crds.enabled=true \
  --set enableCertificateOwnerRef=true \
  --set dns01RecursiveNameserversOnly=true

helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
  --namespace opentelemetry-operator-system \
  --create-namespace \
  --set "manager.collectorImage.repository=otel/opentelemetry-collector-k8s" \
  --set admissionWebhooks.certManager.enabled=false \
  --set admissionWebhooks.autoGenerateCert.enabled=true

Note: this script is included for convenience at helm/deps.sh.

Install The Deno Cluster Helm Chart

Terraform should have created a file called values.yaml in the working directory, make sure it exists before installing the chart with the following command:

⚠️ The Helm chart must be installed into the default namespace.

helm install --namespace=default -f ./values.yaml deno-cluster ../helm/deno-cluster

Create a Deployment

In the tools directory, we've included a command line utility that creates new deployments. You can use it as follows to deploy your first "hello world" app.

Note: substitute <cluster_domain> for the value you specified, e.g. mycluster.deno-cluster.net. Note: substitute <code-storage-bucket>for the value from the terraform output, e.g.deno-cluster-01-code-storage-f65ef9c1.

../tools/ddng deploy \
  -s ../examples/hello \
  -d hello.<cluster_domain> \
  --s3-bucket <code-storage-bucket>