Looks like a nice idea. We will need deployments for each OODT component in that case right?
On Thu, 18 Apr 2019 at 16:00, Tom Barber <t...@spicule.co.uk> wrote: > Just a quick link to somewhere else that I like the pattern of: > > https://docs.arangodb.com/devel/Manual/Tutorials/Kubernetes/ > > These folks have knocked up a few custom Kubernetes operators for ArangoDB > that once you have deployed means to launch a new database all you have to > do is: > > apiVersion: "database.arangodb.com/v1alpha" > kind: "ArangoDeployment" > metadata: > name: "single-server" > spec: > mode: Single > > Or similar. > > If we could do something like this for OODT, where when you want to launch > an instance you just define it as a OODT deployment type to launch a new FM > or whatever, that would be pretty sweet and make it reasonably easy to > build a scale out, K8S OODT. > > -- > > > Spicule Limited is registered in England & Wales. Company Number: > 09954122. Registered office: First Floor, Telecom House, 125-135 Preston > Road, Brighton, England, BN1 6AF. VAT No. 251478891. > > > > > All engagements > are subject to Spicule Terms and Conditions of Business. This email and > its > contents are intended solely for the individual to whom it is addressed > and > may contain information that is confidential, privileged or otherwise > protected from disclosure, distributing or copying. Any views or opinions > presented in this email are solely those of the author and do not > necessarily represent those of Spicule Limited. The company accepts no > liability for any damage caused by any virus transmitted by this email. If > you have received this message in error, please notify us immediately by > reply email before deleting it from your system. Service of legal notice > cannot be effected on Spicule Limited by email. >
