Without k8s cluster, how to deploy milvus distributed cluster on multiple machines? - deployment

If I don't have a k8s cluster, I need to deploy a Milvus distributed cluster on multiple machines. How should I do this? Is it possible to use the docker-compose way?

Related

Is it possible to deploy Kubernetes on a single web server?

Good afternoon!
In my study of Kubernetes, I got to the practice of deploying Kuber on the server. There are different deployment scenarios. I chose kubespray. Can you tell me if you can somehow deploy kuber on a host? Or is it necessary to create virtual machines, set up a network between them and only then deploy the cluster?
Node: A node may be a virtual or physical machine, depending on the cluster. Each node is managed by the control plane and contains the services necessary to run Pods.
You can deploy single Node Kubernetes
For local (development, test etc) purposes:
minikube
kind
...
For production:
k3s
k0s
...
And, of course, you can create separate nodes under one "machine." And use them as worker nodes, but the above solutions are simpler.

Add on-premise CockroachDB node to a cluster hosted in Kubernetes

I'm planning to deploy a small Kubernetes cluster (3x 32GB Nodes). I'm not experienced with K8S and I need to come up with some kind of resilient SQL database setup and CockroachDB seems like a great choice.
I wonder if it's possible to relatively easy deploy a configuration, where some CockroachDB instances (nodes?) are living inside the K8S cluster, but at the same time some other instances live outside the K8S cluster (2 on-premise VMs). All those CockroachDB would need to be considered a single CockroachDB cluster. It might be also worth noting that Kubernetes would be hosted in the cloud (eg. Linode).
By relatively easy I mean:
simplish to deploy
requiring little maintenance
Yes, it's straight forward to do a multi-cloud deployment of CRDB. This is one of the great advantages of cockroachdb. Simply run the cockroach start command on each of the VMs/pods running cockroachdb and they will form a cluster.
See this blog post/tutorial for more info: https://www.cockroachlabs.com/blog/multi-cloud-deployment/

What's the easiest way to setup Spinnaker in lab?

I am new to Spinnaker. I want to setup Spinnaker in my lab to test some pipeline deployments to K8s. I read through a lot of videos and websites teaching how to setup Spinnaker using Helm, Hal, Operator, etc. The steps and requirements are quite complex and I am struggling which method I should take
For my lab environment, I have 3 VM running in CentOS (bare metal) and built a Kubernetes cluster on them (1 master and 2 slave nodes). And now I want to setup Spinnaker to test microservice deployment on this k8s cluster in an easy and quick way
Some of my doubts
If I chose Spinnaker on Kubernetes cluster, do I need to setup another new k8s cluster? Or I can use the same cluster that already has several microservices running on it?
If I chose Spinnaker on VM, guess I need to spin up a new Ubuntu machine instead of setting in on my existing CentOS machine?
Any suggestion is welcome. Thanks!

How can I identify if the akka cluster is running on the kubernetes?

My akka cluster system can deployed both by VMs and kubernetes, how can I identify if the akka cluster is running on the kubernetes so that I do not need to config the cluster seeds node?
An easy way is just to identify if there has the namespace file in the system.
/var/run/secrets/kubernetes.io/serviceaccount/namespace

Can I setup a K8S cluster in VMs with different IP ranges?

I managed to install a 3-node cluster on VMs within the same network.
But is there a way to install a multi-node K8S cluster on VMs with different IP ranges? (VMs which are not located in the same network)
The reason for this question is the scenario that I have in mind:
I need to deploy a micro-service application (written in Java) with K8S. I made docker images from each service in my application and its working locally.
I plan to have each service to be run in a separate physical location (within different networks)
For this I need a multi-node cluster, but each node will get different IP range. Is this possible?
if there is a connectivity among the three nodes then i dont see any reason why you cant setup multi node cluster.
note that kubernetes needs the machines to be closer. because lot of calls happen between api server, kubelet, kube-proxy. it would hit cluster and application performance.