Deviation from expected behavior:
Getting Started and Documentation
For installation, deployment, and administration of the NFS storage provider, see our Documentation.
Expected behavior:
Page can be visited. But page was not found, and this url didn't work either.
How to reproduce it (minimal and precise):
File(s) to submit:
Cluster CR (custom resource), 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.
Environment:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Cloud provider or hardware configuration:
Rook version (use rook version inside 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 health in the Rook Ceph toolbox):
travisn
commented
2 years ago
Is this a bug report or feature request?
Deviation from expected behavior: Getting Started and Documentation For installation, deployment, and administration of the NFS storage provider, see our Documentation.
Expected behavior: Page can be visited. But page was not found, and this url didn't work either. How to reproduce it (minimal and precise):
File(s) to submit:
cluster.yaml, if necessaryCrashing 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 theinsert codebutton from the Github UI. Read Github documentation if you need help.Environment:
uname -a):rook versioninside of a Rook Pod):ceph -v):kubectl version):ceph healthin the Rook Ceph toolbox):