# Do dgraph cloud infrastructure as code?

**URL:** <https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528>\
**Category:** Dgraph Cloud\
**Tags:** kind:question\
**Created:** [July 15, 2022, 8:09am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528 "2022-07-15T08:09:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![SuperCipher](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/supercipher/32/8876_2.png) [@SuperCipher](https://discuss.dgraph.io/u/SuperCipher)\
**Post date:** [July 15, 2022, 8:09am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/1 "2022-07-15T08:09:38Z")

</div>

Does Dgraph cloud have IaC so I can include the cloud configuration in my GitOp?  
Thanks.

---

<div class="post-metadata">

**Author:** ![roshan](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/roshan/32/6336_2.png) [@roshan](https://discuss.dgraph.io/u/roshan)\
**Post date:** [July 16, 2022, 2:52am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/2 "2022-07-16T02:52:21Z")

</div>

There’s some [official helm charts](https://github.com/dgraph-io/charts) you can use. When I worked at Dgraph we managed these charts via the [helm terraform provider](https://registry.terraform.io/providers/hashicorp/helm/latest/docs), but like any helm chart, you can probably use it w/ any k8s lifecycle management tooling that supports helm.

---

<div class="post-metadata">

**Author:** ![joaquin](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/joaquin/32/2619_2.png) [@joaquin](https://discuss.dgraph.io/u/joaquin)\
**Post date:** [July 17, 2022, 1:50am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/3 "2022-07-17T01:50:12Z")

</div>

Also, we’re on artifact hub: [dgraph 0.0.19 · helm/dgraph](https://artifacthub.io/packages/helm/dgraph/dgraph)

Dgraph has built-in support for observability, so one can use tools like [Prometheus](https://prometheus.io) for metrics and [Jaeger](https://www.jaegertracing.io/) for tracing. Given [gRPC](https://grpc.io/) support of Dgraph Alpha endpoints, service meshes like [Linkerd](https://linkerd.io/) and [Istio](https://istio.io/) would work well for this scenario, adding automatic mTLS between endpoints as well as traffic monitoring. With these options available, this allows you to explore trends with progressive deployment tools like [ArgoCD](https://argoproj.github.io/cd/), [FluxCD](https://fluxcd.io/), or [Spinnaker](https://spinnaker.io/).

I wrote some blogs about Dgraph and [Linkerd](https://linkerd.io/) and [Istio](https://istio.io/) service meshes, combined with using network policies (internal Kubernetes firewalls) using [Calico](https://projectcalico.docs.tigera.io):

- [AKS with Istio Service Mesh. Securing traffic with Istio service… | by Joaquín Menchaca (智裕) | Medium](https://joachim8675309.medium.com/istio-service-mesh-on-aks-1b6ed16f6890)
- [AKS with Linkerd Service Mesh. Securing internal traffic with Linkerd… | by Joaquín Menchaca (智裕) | Medium](https://joachim8675309.medium.com/linkerd-service-mesh-on-aks-a75d60ef4f5a)

These articles are both on AKS, but should work with GKE, EKS, and other Kubernetes.

---

<div class="post-metadata">

**Author:** ![amaster507](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amaster507/32/4123_2.png) [@amaster507](https://discuss.dgraph.io/u/amaster507)\
**Post date:** [July 17, 2022, 4:53am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/4 "2022-07-17T04:53:34Z")

</div>

Are you part of the official core team again?

---

<div class="post-metadata">

**Author:** ![SuperCipher](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/supercipher/32/8876_2.png) [@SuperCipher](https://discuss.dgraph.io/u/SuperCipher)\
**Post date:** [July 17, 2022, 5:05am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/5 "2022-07-17T05:05:45Z")

</div>

No I’m not part of office core team.

---

<div class="post-metadata">

**Author:** ![SuperCipher](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/supercipher/32/8876_2.png) [@SuperCipher](https://discuss.dgraph.io/u/SuperCipher)\
**Post date:** [July 17, 2022, 5:08am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/6 "2022-07-17T05:08:32Z")

</div>

Thank you for the answer.  
To clarify my question I mean the Dgraph cloud (Saas) part of the Dgraph cloud not the self host one.  
Thank you.

---

<div class="post-metadata">

**Author:** ![joaquin](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/joaquin/32/2619_2.png) [@joaquin](https://discuss.dgraph.io/u/joaquin)\
**Post date:** [July 18, 2022, 7:35am UTC](https://discuss.dgraph.io/t/do-dgraph-cloud-infrastructure-as-code/17528/7 "2022-07-18T07:35:25Z")

</div>

> [@SuperCipher](#):
>
> Does Dgraph cloud have IaC so I can include the cloud configuration in my GitOp?  
> Thanks.

Then I am not sure what you mean. Do we use gitops or is our cloud code available? The Dgraph cloud has an endpoint that you can use. Someone could perhaps write a Terraform provider to do things like upload a schema or upsert some predicates. Typically, most would use one of the gRPC client libraries: official ones in go, python, C#, JS, Java, and community supported ones in Rust, Elixir, and Ruby.
