public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-10-05 13:38:56 +02:00
Code Issues Projects Releases Wiki Activity

some updates

Browse Source
This commit is contained in:
Felix Kunde
2020-07-10 09:12:26 +02:00
committed by GitHub
parent e49797c992
commit 3a6b3ef9fa
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/ISSUE_TEMPLATE/postgres-operator-issue-template.md
+3 -3
View File
@@ -9,11 +9,11 @@ assignees: ''
Please, answer some short questions which should help us to understand your problem / question better?
- **Which version of the operator are you using?** e.g. v1.5.0
- **Which image of the operator are you using?** e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.5.0
- **Where do you run it - cloud on metal? Kubernetes or OpenShift?** [AWS K8s | GCP ... | Bare Metal K8s]
- **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.
- Please, check the operator, pod (Patroni) and postgresql 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 opening issues in the respective repos.