Greg greg
  • Joined on 2018-11-05
greg created pull request kosmos/chef#70 2019-06-21 15:41:21 +00:00
Switch to our own fork of the poise-javascript cookbook
greg pushed to feature/5-poise-javascript at kosmos/chef 2019-06-21 15:41:05 +00:00
80526e3396 Switch to our own fork of the poise-javascript cookbook
greg commented on issue kosmos/chef#5 2019-06-21 14:15:38 +00:00
Prevent the nodejs applications restarting on every Chef run

I have started from the unreleased master branch of poise-javascript (rake chef:build). That includes a change that supports the new behavior of npm install, writing "up to date" to stdout when no changes have been performed.

greg created pull request kosmos/chef#69 2019-06-20 10:49:06 +00:00
Add email notifications for failed certbot runs
greg pushed to bugfix/3-systemd_email_notifications at kosmos/chef 2019-06-20 10:48:23 +00:00
3a693efcd6 Add email notifications for failed certbot runs
greg commented on issue kosmos/gitea.kosmos.org#28 2019-06-20 10:09:08 +00:00
Update the documentation, Ark is now Velero

The repo doesn't contain example config files anymore, you install velero with the install command now: https://velero.io/docs/v1.0.0/gcp-config/#install-and-start-velero

greg commented on issue kosmos/gitea.kosmos.org#28 2019-06-20 09:59:08 +00:00
Update the documentation, Ark is now Velero

What config files? I didn't remove any config files

greg deleted branch bugfix/3-certbot_email_notifications from kosmos/chef 2019-06-20 09:26:28 +00:00
greg commented on issue kosmos/gitea.kosmos.org#28 2019-06-20 09:18:02 +00:00
Update the documentation, Ark is now Velero

Ready to merge

greg closed issue kosmos/gitea.kosmos.org#27 2019-06-20 09:16:18 +00:00
Ark backups stopped being performed
greg commented on issue kosmos/gitea.kosmos.org#27 2019-06-20 09:16:18 +00:00
Ark backups stopped being performed

I have also deleted the heptio-ark namespace and the matching service account and IAM. Closing this one

greg commented on issue kosmos/gitea.kosmos.org#27 2019-06-20 09:13:51 +00:00
Ark backups stopped being performed

Hooray, that did the trick:

greg commented on issue kosmos/gitea.kosmos.org#27 2019-06-19 16:38:32 +00:00
Ark backups stopped being performed

I ended up switching to Velero 1.0 (Ark got renamed at version 0.11) using the new installation process that's part of the velero binary and using a new bucket. I could not figure out what was wrong with the current bucket. The same error was happening with velero as it did with our previous Ark setup.

greg created pull request kosmos/gitea.kosmos.org#28 2019-06-19 16:35:47 +00:00
Update the documentation, Ark is now Velero
greg pushed to feature/ark_to_velero at kosmos/gitea.kosmos.org 2019-06-19 16:35:18 +00:00
a3fa72bb56 Update the documentation, Ark is now Velero
greg opened issue kosmos/gitea.kosmos.org#27 2019-06-19 13:53:12 +00:00
Ark backups stopped being performed
greg commented on issue kosmos/chef#68 2019-06-19 12:06:12 +00:00
WIP: Replace the certbot systemd unit with a cron job with notifications

You're right, I misunderstood, that would work with the cerbot systemd timer as it is (systemctl status --full certbot will contain the previous error). I'm going to close this and reopen another pull request that does it with a OnFailure section on the certbot service instead

greg closed pull request kosmos/chef#68 2019-06-19 12:06:12 +00:00
WIP: Replace the certbot systemd unit with a cron job with notifications
greg pushed to bugfix/3-certbot_email_notifications at kosmos/chef 2019-06-19 09:11:10 +00:00
6f98d07942 Add the quiet switch to the certbot command
greg commented on issue kosmos/chef#68 2019-06-19 09:09:17 +00:00
WIP: Replace the certbot systemd unit with a cron job with notifications

Damnit, certbot is using stderr to output warnings, so we got an email when it ran at midnight: