Files
velero/.github/ISSUE_TEMPLATE/bug_report.md
Nolan Brubaker c1a817b4e9 Use current info in bug template
The binary, deployment, and namespace have yet to change for most users,
so make sure the bug template has the correct information when filing.

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>
2019-02-05 16:11:56 -05:00

1.0 KiB

name, about
name about
Bug report Tell us about a problem you are experiencing

What steps did you take and what happened: [A clear and concise description of what the bug is, and what commands you ran.)

What did you expect to happen:

The output of the following commands will help us better understand what's going on: (Pasting long output into a GitHub gist or other pastebin is fine.)

  • kubectl logs deployment/ark -n heptio-ark
  • ark backup describe <backupname> or kubectl get backup/<backupname> -n heptio-ark -o yaml
  • ark backup logs <backupname>
  • ark restore describe <restorename> or kubectl get restore/<restorename> -n heptio-ark -o yaml
  • ark restore logs <restorename>

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version (use ark version):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):