search

timescale / helm-charts

Configuration and Documentation to run TimescaleDB in your Kubernetes cluster
Apache License 2.0
264 stars 222 forks source link

Support for Azure and gcp #143

Closed utx0 closed 4 years ago

utx0 commented 4 years ago

Hey guys,

I see in the readme that this chart only supports AWS. Can anyone expand on what might be needed for support to be extended to Azure and/or GCP?

Thanks

feikesteenbergen commented 4 years ago

Even though we don't support it, We've run a few deployments on GCP. We haven't tried Azure yet.

The only thing very specifically required is an S3 (compatible) api for the backup, everything else should work on any Kubernetes deployment.

It's a bit dated, but here for example is a trial with GKE on GCP: https://github.com/timescale/timescaledb-kubernetes/pull/35

feikesteenbergen commented 4 years ago

@lukekhamilton I don't think there's anything in this Chart that would not make it work on Azure/GCP, Can we close this issue?

utx0 commented 4 years ago

Yeah close away.

Thanks

On Mon, 18 May 2020 at 6:11 pm, Feike Steenbergen notifications@github.com wrote:

@lukekhamilton https://github.com/lukekhamilton I don't think there's anything in this Chart that would not make it work on Azure/GCP, Can we close this issue?

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/timescale/timescaledb-kubernetes/issues/143#issuecomment-630019372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAWDI2W7MIQK5SAQ24UBLDRSDUS5ANCNFSM4MKNOLRQ .

-- Regards,

Luke Hamilton Adviser & Consultant | Senior Software Engineer | Solution Architect

(+61) 488 113 380 Stone and Chalk, The Goods Shed North, 710 Collins St, Docklands VIC 3008, Australia

This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must not use, copy, distribute or disclose it to anyone other than the addressee. If you have received this message in error please return the message to the sender by replying to it and then delete the message from your computer. Internet emails are not necessarily secure. MettaData does not accept responsibility for changes made to this message after it was sent.