Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tip for kops users. #35

Merged
merged 1 commit into from
Oct 17, 2017
+29 −0
Merged

Add tip for kops users. #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,35 @@ given, it will create a daily snapshot of the volume. It will keep
snapshot. If the daemon is not running for a while, it will still
try to approximate your desired snapshot scheme as closely as possible.

### A tip for kops users

*k8s-snapshots* need EBS and S3 permissions to take and save snapshots. Under
the [kops](https://github.com/kubernetes/kops/) IAM Role scheme, only Masters
have these permissions. The easiest solution is to run k8s-snapshots on
Masters.

To run on a Master, we need to:
* [Overcome a Taint](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/)
* [Specify that we require a Master](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/)

To do this, add the following to the above manifest for the k8s-snapshots
Deployment:

```
spec:
...
template:
...
spec:
...
tolerations:
- key: "node-role.kubernetes.io/master"
operator: "Equal"
value: ""
effect: "NoSchedule"
nodeSelector:
kubernetes.io/role: master
```

How do the deltas work
----------------------
Expand Down