=================
The majority of setup for the cluster is handled by the various bash scripts, however the Cert Manager and HTTPS configuration of this deployment does require a custom domain along with DNS entries to be updated so that the ingress controller can route traffic to the Phylax service and so that Cert Manager can validate the domain.
I did this by just getting a cheap domain and setting up the DNS in Cloudflare. This was a simple task and can be done in a few minutes.
- Order a cheap domain from a domain registrar, like Namecheap
- Create an account on Cloudflare and add the domain to your account. Follow the instructions on Cloudflare's domain transfer guide.
If you currently have a domain and DNS provider, you can use that just as easily.
Lastly, you will need to update the cluster/overlays/prod/ingress-patch.yaml file with your domain names. Simply replace the value idkthisisademo.lol with your domain.
Use the aks-cluster.sh script to create the AKS cluster. This does require you to authenticate to Azure with the az CLI. If you don't currently have a subscription, you can sign up for a free trial and get $200 in credits to use for 30 days here.
az login
./cluster/aks-cluster.shWe use bootstrap-k8s.sh to install the Nginx Ingress Controller and Cert Manager. This script also creates the Phyalx deployment from the prod overlay folder. It will output a Public IP address you can use to create an A record in your DNS provider.
./cluster/bootstrap-k8s.shYou should now be able to access the Phylax service with the domain you set up. You can view the pods and services with kubectl by running kubectl get -all -n phylax-prod.
To create a separate deployment, simply perform the following.
cp -r phylax/overlays/prod phylax/overlays/<name>Update the kustomization.yaml file in the new overlay folder to use a new namespace by changing the value of namespace:.
Update the ingress-patch.yaml file in the new overlay folder to use your new domain.
Then run kubectl apply -k phylax/overlays/<name> to deploy the new environment.
Kustomize makes it easy to update an image in an overlay.
Simply run kustomize edit set image ghcr.io/phylax-systems/phylax:<version> and then run kubectl apply -k phylax/overlays/<name> to update the deployment.
Environment variables are handled by Kustomize's ConfigMapGenerator. Each overlay contains a .env file, this is where new environment variables can be added. When applied with kubectl apply -k phylax/overlays/<name>, the ConfigMap will be updated, and the deployment will be updated with the new environment variables.