Kubernetes in VPS

luvguru69

Newbie
Joined
Dec 11, 2020
Messages
18
Reaction score
11
It seems to me that various VPS providers on BHW are cheaper than using a generic cloud option(AWS, GCP, Azure).

It got me thinking that if I could bootstrap a Kubernetes server on one of these VPS providers, I could save on compute costs.

Has anyone done this before? If so, any pointers to give out before attempting?
 
Last edited:
It seems to me that various VPS providers on BHW are cheaper than using a generic cloud option(AWS, GCP, Azure).

It got me thinking that if I could bootstrap a Kubernetes server on one of these VPS providers, I could save on compute costs.

Has anyone done this before? If so, any pointers to give out before attempting?
Whenever someone mentions Kubernetes, the first question I ask is why do you need Kubernetes. Most often than not, they don't need kubernetes.

VPS is cheap enough, AWS offers free credits if you look hard enough, what are you trying to do with kubernetes?
 
Whenever someone mentions Kubernetes, the first question I ask is why do you need Kubernetes. Most often than not, they don't need kubernetes.

VPS is cheap enough, AWS offers free credits if you look hard enough, what are you trying to do with kubernetes?

Current Set Up:
Front End
Custom Built Frontend - Hosted in cloudfare DNS

Backend
API and NGINX Reverse Proxy - Custom server built with GO running in docker on its own compute instance
Database - Document Datastore running in docker compose on its on compute instance

I have new features queued up that I will be putting into production soon. These features are their own microservices.

To reduce complexity, I'm thinking of moving to kubernetes instead of managing different compute instances manually.
 
Current Set Up:
Front End
Custom Built Frontend - Hosted in cloudfare DNS

Backend
API and NGINX Reverse Proxy - Custom server built with GO running in docker on its own compute instance
Database - Document Datastore running in docker compose on its on compute instance

I have new features queued up that I will be putting into production soon. These features are their own microservices.

To reduce complexity, I'm thinking of moving to kubernetes instead of managing different compute instances manually.
You don't need Kubernetes :)
If you want to learn k8s, by all means, go for it. It is a complicated technology.

Reminds me of this meme
1*e9UvQdXCIf9QKIpo8Br3Wg.png


Why not deploy your microservices into small elastic beanstalk/ec2 instances? It is super easy to manage them unless you have 20 + services.
 
To reduce complexity, I'm thinking of moving to kubernetes instead of managing different compute instances manually.
Complexity as in what? Setup? I don't think your kubernetes instances will be any less complicated than your docker instance anyway. kubernetes isn't for everyone. Even if it justifies being your solution, it might be hard to troubleshoot and maintain if you are not easy with the technology. If you just want it for milking a server out, meh.. I don't think it's worth. But anyway.. Research!
 
You don't need Kubernetes :)
If you want to learn k8s, by all means, go for it. It is a complicated technology.

Reminds me of this meme
1*e9UvQdXCIf9QKIpo8Br3Wg.png


Why not deploy your microservices into small elastic beanstalk/ec2 instances? It is super easy to manage them unless you have 20 + services.

Sure that makes sense. I guess for the time being, my time could be spent elsewhere and I can keep the current setup as is.

Complexity as in what? Setup? I don't think your kubernetes instances will be any less complicated than your docker instance anyway. kubernetes isn't for everyone. Even if it justifies being your solution, it might be hard to troubleshoot and maintain if you are not easy with the technology. If you just want it for milking a server out, meh.. I don't think it's worth. But anyway.. Research!

My thinking was, invest the time to build out the infrastructure. Then when it comes time to add services getting them operational would be a breeze. Also I believe that automating a CI/CD environment could be accomplished in a Kubernetes cluster as well. As far as experience goes, all of the places I worked utilized Kubernetes clusters(managed by dev-ops teams) for their platforms so I do have some experience using the technology.
 
My thinking was, invest the time to build out the infrastructure. Then when it comes time to add services getting them operational would be a breeze. Also I believe that automating a CI/CD environment could be accomplished in a Kubernetes cluster as well. As far as experience goes, all of the places I worked utilized Kubernetes clusters(managed by dev-ops teams) for their platforms so I do have some experience using the technology.
If you do have some experience in this technology and it is financially feasble for you to move on, there's no reason why you should not. I haven't tried a lot of providers here. I have tried Hyonix (for myself) and Hostwinds (for clients). Hyonix, according to my test was at par. Hostwinds was really bad (sorry guys, just sharing my experience), but you could try contacting them before buying. That's the feedback from my side. May be wait for other people to share their experience.

P.S> I never tried anything related to Kubernetes on any of the two I mentioned, so you are on your own lol..
 
If you do have some experience in this technology and it is financially feasble for you to move on, there's no reason why you should not. I haven't tried a lot of providers here. I have tried Hyonix (for myself) and Hostwinds (for clients). Hyonix, according to my test was at par. Hostwinds was really bad (sorry guys, just sharing my experience), but you could try contacting them before buying. That's the feedback from my side. May be wait for other people to share their experience.

P.S> I never tried anything related to Kubernetes on any of the two I mentioned, so you are on your own lol..
Thanks for the feedback I appreciate it. Looks like I'm better off just sticking to platforms I know instead of trying to save a quick buck.
 
Thanks for the feedback I appreciate it. Looks like I'm better off just sticking to platforms I know instead of trying to save a quick buck.
I think so too.
P.S. What would you use for the cluster if you had to go with the market leaders? I don't see people talking about Kubernetes everyday here, so I thought I would ask. :p
 
I think so too.
P.S. What would you use for the cluster if you had to go with the market leaders? I don't see people talking about Kubernetes everyday here, so I thought I would ask. :p

--Edit--
Guess I read your reply wrong. Currently using GCP so many switching to their managed GKE would be easiest. Other than that, probably try to bootstap the cluster myself in AWS EC2 instances if GKE was too expensive.

Details of current infrastructure are in an above reply.

As far as the actual product goes it's a website/web-application. I started building it in the summer and didn't have any idea about how IM worked. I recently found BHW and noticed that the site started getting some organic traffic just with pure onsite optimization(and time). Turns out when I built it, I inadvertently captured some low-competition keywords.

It's not a typical blog website but I guess would be categorized as a content website in a music niche. To increase sickness and quality of content, I'm attempting to add features for user interaction(currently content is somewhat 'static'). It's not monetized but I believe once built out, I can either utilize CPC or some other strategy.
 
Last edited:
--Edit--
Guess I read your reply wrong. Currently using GCP so many switching to their managed GKE would be easiest.
Thanks for the edit. I was about to quote you coz I didnt find the company lol. Thanks for the knowledge!
 
Back
Top