search

vaticle / typedb-docs

TypeDB Documentation
25 stars 72 forks source link

Image not found - graknlabs/grakn-cluster:2.0.3 #526

Closed Tin-Nguyen closed 3 years ago

Tin-Nguyen commented 3 years ago

Description

I'm trying to deploy TypeDB (Grakn) to AWS EKS cluster using HELM from the helm repo https://repo.vaticle.com/repository/helm/.

Recently, even I'm following strictly the guidance at https://github.com/vaticle/docs/blob/master/05-typedb-cluster/02-kubernetes.md, I still cannot resolve the issue - ImagePullBackOff (Image not found)

I see the pod is running under the image graknlabs/grakn-cluster:2.0.3. But I don't see that container image in Docker Hub like the guidance describes.

It seems we need to update the helm package?

lolski commented 3 years ago

Hi @Tin-Nguyen!

TypeDB Cluster is our commercial offering. Once you've acquired a license, you can use that license to retrieve the image.

If that is something that you are interested in you should speak to @tomassabat .

Tin-Nguyen commented 3 years ago

Thanks @lolski , where can I find out the benefits of using TypeDB Cluster comparing with the graknlabs/grakn image running with multiple replicas?

lolski commented 3 years ago

comparing with the graknlabs/grakn image running with multiple replicas?

It is not possible to run TypeDB (Grakn) in a "multiple replicas" setting. TypeDB can't replicate data from one to another. That's what TypeDB Cluster is for.

In short, TypeDB Cluster provides high-availability, scalability, authentication, and network encryption.

We are in the process of revamping the docs and presently you won't find a comprehensive documentation. My talk at Grakn Cosmos 2021 would be the best place to learn about the feature set: https://www.youtube.com/watch?v=LJxqlei_ir0

Tin-Nguyen commented 3 years ago

Thank you. It's more clear now. I did test and figured it out, the data isn't being replicated to other nodes with graknlabs/grakn image.