Verified Commit 59e4118d authored by justin's avatar justin

Update website commit, ingress commit, and patch-version.

parent b1bb15f8
......@@ -7,6 +7,10 @@
- [Added](#added)
- [Changes](#changes)
- [Removed](#removed)
- [1.1.1 - 2019-09-24](#111-2019-09-24)
- [Added](#added-1)
- [Changes](#changes-1)
- [Removed](#removed-1)
- [1.1.0 - 2019-08-23](#110-2019-08-23)
- [Added](#added-1)
- [Changes](#changes-1)
......@@ -38,7 +42,14 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
## [Unreleased]
### Added
### Changes
### Removed
## [1.1.1] - 2019-09-24
### Added
### Changes
- Updated boxomon to [v0.3.2](https://gitlab.palpant.us/justin/boxomon/-/tags/v0.3.2)
- Updated GKE cert-manager to v0.10.0
- Updated personal website.
### Removed
## [1.1.0] - 2019-08-23
......@@ -163,7 +174,8 @@ Lastly, I have split up the single mono-repo into individual repos to support si
- HAProxy, all instances
- Most of the 9s in my previous uptime. But they will be back, and better than ever!
[Unreleased]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v1.1.0...HEAD
[Unreleased]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v1.1.1...HEAD
[1.1.1]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v1.1.0...v1.1.1
[1.1.0]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v1.0.0...v1.1.0
[1.0.0]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v0.2.0...v1.0.0
[0.2.0]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v0.1.1...v0.2.0
......
......@@ -75,15 +75,15 @@ MySQL version: `5.7`
### Cluster-hosted services
#### Ingress
Ingress is provided by [ingress-nginx](https://github.com/kubernetes/ingress-nginx), installed with Helm (chart: stable/ingress-nginx) and [cert-manager](https://github.com/jetstack/cert-manager) has been installed with Helm (chart: stable/cert-manager) to get certificates for requested domains. Configuration is managed completely in source code, stored in [palpantlab-ingress](https://gitlab.palpant.us/palpantlab-ingress). DNS CNAMEs are managed with Google Domains to get traffic to redirect to the public IP of the single GKE LoadBalancer of the NGINX ingress service. I chose nginx-ingress because I had previous experience configuring it, and the Google L7 Ingress creates a _significant_ number of routing rules in GCP that cost a lot (when you're at the budget levels I'm working at), while with nginx-ingress I create only Kubernetes objects and consume CPU that I am already paying for.
Ingress is provided by [ingress-nginx](https://github.com/kubernetes/ingress-nginx), installed with Helm (chart: stable/ingress-nginx) and [cert-manager](https://github.com/jetstack/cert-manager) has been installed with Helm (chart: jetstack/cert-manager) to get certificates for requested domains. Configuration is managed completely in source code, stored in [palpantlab-ingress](https://gitlab.palpant.us/palpantlab-ingress). DNS CNAMEs are managed with Google Domains to get traffic to redirect to the public IP of the single GKE LoadBalancer of the NGINX ingress service. I chose nginx-ingress because I had previous experience configuring it, and the Google L7 Ingress creates a _significant_ number of routing rules in GCP that cost a lot (when you're at the budget levels I'm working at), while with nginx-ingress I create only Kubernetes objects and consume CPU that I am already paying for.
ingress-nginx helm chart: `nginx-ingress-0.31.0`
nginx-ingress-controller image: `quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.21.0`
cert-manager helm chart: `cert-manager-v0.4.1`
cert-manager helm chart: `cert-manager-v0.10.0`
cert-manager image: `quay.io/jetstack/cert-manager-controller:v0.5.2`
cert-manager image: `quay.io/jetstack/cert-manager-controller:v0.0.10.0`
#### Source control with locally hosted Gitlab
All of this actually started with hosting a private GitLab instance, https://gitlab.palpant.us, which ran on an Ubuntu virtual machine. That application not runs as a cloud-native Helm chart in GKE, and is managed in the submodule [palpantlab-gitlab](https://gitlab.palpant.us/justin/palpantlab-gitlab). It stores all source code for these various projects and GitLab CI/CD connects to both Kubernetes clusters, using them as build slaves and deploying services to them when there are updates.
......
Subproject commit a7995e8aa6c030e57e7fd18b82d710ccdc07e401
Subproject commit 3283daf2745d5d6e8b22781c907038ff63a78522
Subproject commit 8dc559977a75f786e11620f73ef18e97618c4226
Subproject commit c3add5efe64b73b8c13e4386ee567b9c9587b4f6
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment