ingress.yamlfile and make sure that the following complies:
kubernetes.io/ingress.global-static-ip-name: [env]-aimmo-ingressis set.
- host: default-aimmo.codeforlife.education
kubectl create secret tls foo-secret --key=/tmp/tls.key --cert=/tmp/tls.crt. This will require correct authentication which is described above.
ssl-cert-secreton a cluster and creating a new one will hang the game creator as it will not receive information since a certificate authority issue will occur. The solution for this is to delete the game creator pod which will reinstantiate all the games and workers from scratch.
codeforlife-deploy-appengineproject, in the
clusters_setup/terraformdirectory. You can set up the clusters from your machine by following these steps:
gcloudCLI (you can follow the steps in its docs -https://cloud.google.com/sdk/gcloud). Make sure you follow the configuration steps as well: setting our project id and authenticating. We store the Terraform state in a bucket on GCP, so it needs access to it first (and also later for setting up the clusters).
terraform workspace select [environment]where
default, depending on the cluster you want to work on.
terraform apply. This actually runs the
plancommand above first, then it asks you to confirm if you're happy with the changes.
yeson the command above, especially the destroying operations. Make sure the changes are tested on dev/staging first.
host. The values of these will need to be copied to
django_site/kubeconfig.yaml.tmplfor the appropriate environment if the cluster has been recreated: the
b64_cluster_ca_certificatewill go into