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.

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

Service accounts should be restored prior to workload controllers #239

Closed
jhorwit2 opened this issue Dec 9, 2017 · 1 comment
Closed
Assignees
Milestone

Comments

@jhorwit2
Copy link

jhorwit2 commented Dec 9, 2017

$ ark version
Version: v0.6.0
Git commit: v0.6.0
Git tree state: clean

I ran a backup restore earlier and noticed that service accounts were not created before the workload controllers which causes the restore process to take longer and at first it makes it seem like the restore process had an issue. It'd be nice if there was some ordering of restores to avoid unnecessary events and further delay.

$ ark restore create monitoring
Restore "monitoring-20171209222726" created successfully.

$ kba -n monitoring get ds
NAME         DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                         AGE
fluentd      0         0         0         0            0           <none>                                9s
prometheus   0         0         0         0            0           node-role.kubernetes.io/prometheus=   9s

$ kba -n monitoring get sa
NAME      SECRETS   AGE
default   1         47s

$ kba -n monitoring get sa
NAME         SECRETS   AGE
default      1         1m
fluentd      3         33s
prometheus   3         33s

$ kba -n monitoring get ds
NAME         DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                         AGE
fluentd      10        10        10        10           10          <none>                                1m
prometheus   0         0         0         0            0           node-role.kubernetes.io/prometheus=   1m
Events:
  Type     Reason        Age               From        Message
  ----     ------        ----              ----        -------
  Warning  FailedCreate  3m (x14 over 4m)  daemon-set  Error creating: pods "prometheus-" is forbidden: service account monitoring/prometheus was not found, retry after the service account is created
@ncdc
Copy link
Contributor

ncdc commented Dec 11, 2017

Recording our conversation from slack: it is possible to do this, but it's not a default setting. You can edit the config's resourcePriorities. The default, if unset, is namespaces, persistentvolumes, persistentvolumeclaims, secrets, configmaps. You would need to add serviceaccounts to this list. Anything not in the list is restored after all of these.

We will also do a PR to change the default.

@ncdc ncdc added this to the v0.7.0 milestone Dec 11, 2017
@ncdc ncdc self-assigned this Dec 11, 2017
dymurray pushed a commit to dymurray/velero that referenced this issue Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants