mirrors/kube-arangodb
1
0
Fork 0
mirror of https://github.com/arangodb/kube-arangodb.git synced 2024-12-14 11:57:37 +00:00
Code Activity

Markdown fixes

Browse source
This commit is contained in:
Ewout Prangsma 2018-06-14 13:20:41 +02:00
parent baaf3df656
commit 812b861be4
No known key found for this signature in database
GPG key ID: 4DBAD380D93D0698
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/Manual/Deployment/Kubernetes/Troubleshooting.md
View file

@ -70,12 +70,15 @@ There are two common causes for this.
1) The `Pods` cannot be scheduled because there are not enough nodes available. 1) The `Pods` cannot be scheduled because there are not enough nodes available.
This is usally only the case with a `spec.environment` setting that has a value of `Production`. This is usally only the case with a `spec.environment` setting that has a value of `Production`.
Solution: Add more nodes. Solution:
Add more nodes.
1) There are no `PersistentVolumes` available to be bound to the `PersistentVolumeClaims` 1) There are no `PersistentVolumes` available to be bound to the `PersistentVolumeClaims`
created by the operator. created by the operator.
Solution: Use `kubectl get persistentvolumes` to inspect the available `PersistentVolumes` Solution:
and if needed, use the [`ArangoLocalStorage` operator](./StorageResource.md) to provision `PersistentVolumes`. Use `kubectl get persistentvolumes` to inspect the available `PersistentVolumes`
and if needed, use the [`ArangoLocalStorage` operator](./StorageResource.md) to provision `PersistentVolumes`.
### When restarting a `Node`, the `Pods` scheduled on that node remain in `Terminating` state ### When restarting a `Node`, the `Pods` scheduled on that node remain in `Terminating` state