adamhosier
adamhosier
AC: * Images are published to improbable's public docker hub on successful build of master with a short SHA * Pushed image is tagged with latest
Cluster owners should be able to set a backup strategy on their etcd clusters in order to take automated backups of cluster data. Backups must be able to be taken...
running `go test ./... -race` shows a number of warnings. we should address these where possible, and run automated tests with race checking enabled.
We would like to limit the amount of successful/failed `EtcdBackup` resources that are lying around in clusters. The `EtcdBackupSchedule` controller should be adjusted to remove all but the `x` newest...
Defaulting is not currently required, we require all fields to be explicit, but there is a good chance it will be required in the future as the API is modified...
We must be able to serve etcd client traffic over TLS AC: * The cluster resource contains options for supplying certs for serving traffic over TLS
We must be able to encrypt/authenticate traffic sent between cluster peers.
The behaviour of failed backup uploading is currently undefined - some backends may leave partial backups around, which the operator will detect as a complete backup and will not retry....