Sébastien Han
571eaf2308
This is not a recommended workflow but useful if people click on "Don’t see your issue here? Open a regular issue." Signed-off-by: Sébastien Han <seb@redhat.com>
1.7 KiB
1.7 KiB
Is this a bug report or feature request?
- Bug Report
- Feature Request
Bug Report
Expected behavior:
Deviation from expected behavior:
How to reproduce it (minimal and precise):
File(s) to submit:
- Cluster CR (custom ressource), typically called
cluster.yaml, if necessary - Operator's logs, if necessary
- Crashing pod(s) logs, if necessary
To get logs, use kubectl -n <namespace> logs <pod name>
When pasting logs, always surround them with backticks or use the insert code button from the Github UI.
Read Github documentation if you need help.
Feature Request
Are there any similar features already existing:
What should the feature do:
What would be solved through this feature:
Does this have an impact on existing features:
Environment:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a): - Cloud provider or hardware configuration:
- Rook version (use
rook versioninside of a Rook Pod): - Storage backend version (e.g. for ceph do
ceph -v): - Kubernetes version (use
kubectl version): - Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift):
- Storage backend status (e.g. for Ceph use
ceph healthin the Rook Ceph toolbox):