FAQ | This is a LIVE service | Changelog

Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • configurable-maint-window-test
  • v5
  • issue-41-v4-test
  • v4
  • v3
  • temp-raven-override
  • issue-391-alert-node-not-scaling-down-v3
  • v2
  • add-issue_client_certificate
  • rjw57-experiment
  • v1
  • issue-15-workload-identity
  • upgrade_settings
  • add-token-auth
  • cloudrun-configuration
  • expose-client-key
  • 0.11-version
  • 8.0.2
  • 8.0.1
  • 8.0.0
  • 7.4.0
  • 7.3.1
  • 7.3.0
  • 7.2.0
  • 7.1.0
  • 7.0.0
  • 6.0.0
  • 5.2.4
  • 5.2.3
  • 5.2.2
  • 5.2.1
  • 5.2.0
  • 5.1.0
  • 5.0.1
  • 5.0.0
  • 3.1.3
  • 4.0.3
38 results
Blame Permalink
  • Dr Rich Wareham's avatar
    d0129d71
    move cluster maintenance window · d0129d71
    Dr Rich Wareham authored 
    To avoid GMT/BST issues, move the maintenance window from 4-8AM UTC to
1-5AM UTC.

Google requires that the window be at least 4 hours and so this is
different from the 2-5AM specified by #11.

Take the opportunity to tidy up the recurrence specification and to
choose a rounder arbitrary date for the start time.

Closes #11
    d0129d71
    History
    move cluster maintenance window
    Dr Rich Wareham authored 
    To avoid GMT/BST issues, move the maintenance window from 4-8AM UTC to
1-5AM UTC.

Google requires that the window be at least 4 hours and so this is
different from the 2-5AM specified by #11.

Take the opportunity to tidy up the recurrence specification and to
choose a rounder arbitrary date for the start time.

Closes #11
Code owners
Assign users and groups as approvers for specific file changes. Learn more.