James Laverack
James Laverack
#### What type of PR is this: /kind documentation #### What this PR does / why we need it: Release Lead handbook updates and clarifications. #### Which issue(s) this PR...
Currently the restoreagent executes as root in a pod. The etcd pod, which runs as root, expects the data directory to be owned by `root:root`. So the restore agent must...
Implement 'proxy' service to control upload and download of backups during the backup and restore process. See the design document for details (TODO commit design document into git repo 😅)...
When creating the restore pods create them using the same resource limits, resource requests, and affinity rules as the etcd pods will later be created with.
Users of the operator want to monitor backup failures and successes, in particular to alert on failed backups or a lack of successful ones. ## Design A [metric](https://book.kubebuilder.io/reference/metrics.html) will be...
Editing an `EtcdCluster` resource to add, amend, or remove `spec.podTemplate.metadata.annotations` should push those changes down to the underlying pods.
Currently when we connect to etcd from the cluster controller we create a new connection every time. We could save resources by keeping a pool of them available.
We currently use watches to automatically reconcile when something we are observing changes. For resources in the Kubernetes API such as `EtcdCluster`, `EtcdPeer`, `Service`, and `ReplicaSet` this is natively supported....
Currently our end to end testing is executed via [KIND](https://github.com/kubernetes-sigs/kind) (see `make kind`) and targets only the latest version of k8s. We are documented as supporting all versions of Kubernetes...
- One-line PR description: Add first draft of KEP 3344 - Issue link: https://github.com/kubernetes/enhancements/issues/3344 - Other comments: N/A