From ca5c832569b528107f50d35d73157c0375813770 Mon Sep 17 00:00:00 2001 From: Felix Kunde Date: Wed, 8 Jul 2020 17:30:26 +0200 Subject: [PATCH] Update issue templates To help us helping them --- .../postgres-operator-issue-template.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/postgres-operator-issue-template.md diff --git a/.github/ISSUE_TEMPLATE/postgres-operator-issue-template.md b/.github/ISSUE_TEMPLATE/postgres-operator-issue-template.md new file mode 100644 index 000000000..76f939eb9 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/postgres-operator-issue-template.md @@ -0,0 +1,19 @@ +--- +name: Postgres Operator issue template +about: How are you using the operator? +title: '' +labels: '' +assignees: '' + +--- + +Please answer some short question which should help us to understand your problem / question better? + +**Which version of the operator are you using?** e.g. v1.5.0 +**Are you running Postgres Operator in production?** [yes | no] +**Where do you run it? Kubernetes or OpenShift?** [AWS K8s | GCP ... | Bare Metal K8s] +**Type of issue?** [Bug report, question, feature request, etc.] + +Some general remarks when posting a bug report: +- Please, check the operator and postgres pod (Patroni) logs first. When copy pasting many log lines please do it in a separate GitHub gist together with your Postgres CRD and configuration manifest. +- If you feel this issue might be more related to the [Spilo](https://github.com/zalando/spilo/issues) docker image or [Patroni](https://github.com/zalando/patroni/issues), consider to open issues in the respective repos.