Allow deployments to test.geek.zone #10
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CarwynNelson
force-pushed
the
kubernetes-deployment
branch
2 times, most recently
from
446d366
to
939fef1
Compare
Resolves #4. This commit allows members and contributors to deploy their changes to a testing environment. The testing environment is currently a temporary Kubernetes cluster hosted on AWS using their Elastic Kubernetes Service (EKS). CircleCI builds docker images of the django web app and an nginx proxy and then pushes them up to the GeekZone Elastic Container Registry (ECR). CircleCI then applies the kuberenetes configuration located in the `k8s` folder to the kubernetes cluster. Docker images are tagged with the circleci workflow id which is unqiue to every run of the pipeline. The django service is run using Gunicorn and all requests to it are proxied via nginx which serves static assets. There might be a better way of doing this in the long term?
CarwynNelson
force-pushed
the
kubernetes-deployment
branch
from
939fef1
to
42567d4
Compare
|
SAM it baby ;) |
jamesgeddes
approved these changes
Jul 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #4.
This pull request allows members and contributors to deploy their changes to
a testing environment.
The testing environment is currently a temporary Kubernetes cluster
hosted on AWS using their Elastic Kubernetes Service (EKS).
CircleCI builds docker images of the django web app and an nginx proxy
and then pushes them up to the GeekZone Elastic Container
Registry (ECR). CircleCI then applies the kuberenetes configuration
located in the
k8sfolder to the kubernetes cluster.Docker images are tagged with the circleci workflow id which is unqiue
to every run of the pipeline.
The django service is run using Gunicorn and all requests to it are
proxied via nginx which serves static assets. There might be a better
way of doing this in the long term?