What’s the most affordable way to try out OpenShift on AWS?

0
0
Asked By CoolCat1234 On

Hey everyone, I'm looking to experiment with Red Hat OpenShift on AWS (ROSA) and need some advice on pricing. Specifically, I want to know the cheapest feasible option if I go with all on-demand instances. I understand that the costs include both the ROSA service fees and the infrastructure fees. I'm asking because I've heard a lot of horror stories about people ending up with huge AWS bills when testing things out.

4 Answers

Answered By AWSBudgetSaver On

If this is just for testing, try to stick to a single Availability Zone (AZ) to avoid those pesky inter-AZ transfer fees. And keep the number of public IPs low. You can find the minimum deployment requirements here: https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws_classic_architecture/4/html/install_rosa_classic_clusters/deploying-rosa-without-aws-sts#rosa-ec2-instances_prerequisites. If you have an AWS account manager, this might be a good opportunity to ask for some service credits to help with costs.

CoolCat1234 -

Thanks for the heads-up!

Answered By TechieGuru98 On

I'm curious too—what's drawing you to ROSA compared to straight-up EKS?

OpenShiftNerd22 -

I'm really looking to try OpenShift and ROSA since my company is planning to switch over.

Answered By CloudKing77 On

I might not remember all the details, but if you're going with ROSA, you usually need something like m5.xlarge for at least 3 worker nodes. To save some money, you could avoid using private subnets to cut costs on NAT gateways. Also, be cautious with integrations like CloudWatch; I heard they can run up really high bills.

TechieGuru98 -

Yeah, with that many nodes, using a single NAT gateway is definitely cheaper than managing too many public IPs!

Answered By CostCutter25 On

For the cheapest setup, try this:
* Use **ROSA HCP**, **single-AZ**, and **public API/ingress** to avoid NAT charges.
* Start small: **about 2 m5.xlarge workers** and consider adding a **Spot pool** for extra testing without breaking the bank.
* Minimize add-ons—things like CloudWatch can quickly eat up your budget.
* Set short log retention, and if traffic's low, don’t forget to delete the cluster once you’re done. And remember to ask your AWS/Red Hat rep for trial credits if you have one!

CoolCat1234 -

Great advice, I'll definitely reach out for those credits!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.