-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pod has unbound immediate PersistentVolumeClaims #17625
Comments
@KOSSOKO |
@tolusha chectl/0.0.20200810-next.aaf3582 win32-x64 node-v10.22.0 |
pls use |
@tolusha even if it is not a minikube ?I have a real kubernetes cluster |
You mentioned that |
Sorry, let me update it. It is k8S 1.13 |
What does this print ? |
efs-performance flexvolume-huawei.com/fuxiefs 2d1h we use ssd and sata for most of apps we deploye |
So, there is no a default one then use flags |
Thanks, i'm trying it. Command is running Maybe, this documentation should be updated in order to add these two properties in the list of available properties: |
Agree. |
@tolusha even if I added the properties, still have the same issue with following logs.
|
|
|
Probably some leftovers in the namespace. I don't see |
It is working thanks. Now che is downloading the images.
Thanks a lot |
Describe the bug
Times out when scheduling/downloading images.
Logs indicate timeout waiting for postgres volumes to be bound
Che version
latest
Steps to reproduce
ran
chectl server:start --platform k8s --multiuser --domain=che.test.maap --k8spodwaittimeout=300000
Expected behavior
Eclipse che is deployed and a url is generated
Runtime environment: Kubernetes
Kubernetes cluster: 1.13
kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"windows/amd64"}
Unable to connect to the server: dial tcp 90.84.245.177:5443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Screenshots
Logs :
The text was updated successfully, but these errors were encountered: