Update docs and tag v1.2.0.

parent 9a2a9163
......@@ -7,29 +7,33 @@
- [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)
- [1.2.0 - 2019-11-13](#120-2019-11-13)
- [Added](#added-1)
- [Changes](#changes-1)
- [Removed](#removed-1)
- [1.0.0 - 2019-07-01](#100-2019-07-01)
- [1.1.1 - 2019-09-24](#111-2019-09-24)
- [Added](#added-2)
- [Changes](#changes-2)
- [Removed](#removed-2)
- [0.2.0 - 2018-03-05](#020-2018-03-05)
- [1.1.0 - 2019-08-23](#110-2019-08-23)
- [Added](#added-3)
- [Changes](#changes-3)
- [Removed](#removed-3)
- [0.1.1 - 2017-12-05](#011-2017-12-05)
- [1.0.0 - 2019-07-01](#100-2019-07-01)
- [Added](#added-4)
- [Changes](#changes-4)
- [0.1.0 - 2017-11-25](#010-2017-11-25)
- [Removed](#removed-4)
- [0.2.0 - 2018-03-05](#020-2018-03-05)
- [Added](#added-5)
- [Changes](#changes-5)
- [Removed](#removed-4)
- [Removed](#removed-5)
- [0.1.1 - 2017-12-05](#011-2017-12-05)
- [Added](#added-6)
- [Changes](#changes-6)
- [0.1.0 - 2017-11-25](#010-2017-11-25)
- [Added](#added-7)
- [Changes](#changes-7)
- [Removed](#removed-6)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
......@@ -41,8 +45,14 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
## [Unreleased]
### Added
### Changes
### Removed
## [1.2.0] - 2019-11-13
### Added
- Deployed [stackdriver-exporter](https://gitlab.palpant.us/justin/stackdriver-exporter) to export stackdriver methods to Prometheus
- Allocated TLS certificates for prometheus.palpant.us and alertmanager.palpant.us.
- Enabled direct [prometheus access](https://prometheus.palpant.us) from the web behind an OAuth2 proxy
- CronJobs using [rclone](https://rclone.org/) to backup GCS and ubuntu-node-01 to Dropbox in [rclone-to-dropbox](https://gitlab.palpant.us/justin/rclone-to-dropbox)
### Changes
- Allocated additional resources
......@@ -183,7 +193,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.1...HEAD
[Unreleased]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v1.2.0...HEAD
[1.2.0]: https://gitlab.palpant.us/justin/palpantlab-infra/compare/v1.1.1...v1.2.0
[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
......
......@@ -119,7 +119,12 @@ I run the Kubernetes Dashboard built at [kubernetes/dashboard](https://github.co
I've been running this since version 1.8, and have recently upgraded to the 2.0 beta and redeployed.
Kubernetes dashboard version: `v2.0.0-beta2+0.ge9d82f7`
Kubernetes dashboard version: `v2.0.0-beta5`
#### GitLab-based monitoring (Prometheus/Alertmanager/Grafana)
GitLab deploys a nicely-configured monitoring stack as part of its recent Helm charts. This by default comes with an alertmanager, a Grafana server, and a configured Prometheus server. While not completely configurable (new dashboard and account management is difficult), the ability to look at basic metrics with no configuration is pretty nice! To make it even easier, I added a public, authenticated ingress for the Prometheus server at [prometheus.palpant.us](https://prometheus.palpant.us).
I also already had uptime monitoring checks configured via Stackdriver, a separate Google product. Stackdriver is great for this, and the uptime checks are frequent, geographically distributed, track latencies, and the alerting system is very powerful. Unfortunately, metric retention in Stackdriver is limited to 6 weeks only (42 days!!) - too short a time to see changes over time. The dashboarding and query language is also limited. To get around that, I deployed [stackdriver-exporter]() to export these uptime check metrics from Stackdriver to Prometheus, where I have more control over retention and aggregation. stackdriver-exporter also supports exporting arbitrary Stackdriver GCP metrics (like log-derived metrics, compute metrics, SQL server metrics, etc.) - however, the API usage grows rapidly if you want to export these metrics on a regular basis, and Google Cloud charges a high cost for metric-read APIs if you exceed a threshold, so for now I am only exporting the uptime check metrics to limit API usage.
## palpantlab-sfo
A single-node Kubernetes master running "on-prem". This single-node cluster has low-reliability (I frequently reboot it and use it as a personal computer), but is very powerful for simple jobs and those where occasional failures are not significant, providing 16 modern CPU cores, 32 GiB of RAM, access to a NAS with 3TiB of RAID1 storage, and access to a (somewhat dated) NVIDIA GPU.
......
Subproject commit 077b14b371bc5bf1bf7a44721c95419c292488cb
Subproject commit ccedcae4a9172a8bcf84b93433ba76acf1e667ea
Subproject commit baaea127ba048a6045c6bc2349dd07f82ef1d05c
Subproject commit 35a28f7445cfc1d5e53c7f3c747583fa22cff06e
Subproject commit 009e2ec9a212745ca4c17c910d965cc35d1252ab
Subproject commit 8873debf630ab5d1da9f8e6490b68d20e7315a28
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