Actually, I didn't use kind and also did any other opening port. then, is it natural that results to be seen not completely installed like 'STATUS Init:0/1' or that result caused by another reason.
I"m really new to this field like mlops, network engineering , any comments always appreciate to me, thanks.
and right after that,
install helm and also tried to install clearml by this link None
@<1523701087100473344:profile|SuccessfulKoala55> Thank you Jake,
kubectl get services as follows:
Did I understand your statement?
There is not such like elasticsearch service, but clearml-elastic-master(?) I coud see.
I also tried
kubectl get pod clearml-apiserver-795794645f-6msmj
and checked events, the latest event was init-apiserver
so I checked as follos:
kubectl logs -f clearml-apiserver-795794645f-6msmj -c init-apiserver
there was inf. loop of one command line
and it is the first commands of init-apiserver I checked by 'kubectl describe'
Did you use any override values.yaml file for this installation ?
I tried kubernetes installation on virtual box linux environment and checked, as following:
Details will be written here,
btw, judging from screenshots services are ok but pod are not up, especially elastic, redis and mongodb are
Pending so it means k8s didn’t scheduled them for some reason you can find describing these pods
@<1523701827080556544:profile|JuicyFox94> Thank you Valeriano, I also tried to track that pods and I found that there was not any stroage class and PV, so status of (PVC of those pods) was pending. Yesterday I was too confused to keep doing this work. Doing this work, I just went home. Appreciately your guidance encourage me to study more about the relation between pod, PV, PVC, and storage class today.
Thank you again!
@<1523701827080556544:profile|JuicyFox94> any idea?
@<1562610732267212800:profile|FreshCat70> this basically means the apiserver is waiting for connection to the ElasticSearch database, please check that the elasticsearch service is up