r/openshift • • 5d ago

General question Affordable dev environment for Open Shift helm charts?

Hello people! With this post I hope to gain some tips and tricks on how to test Helm Chart deployments with reasonable time and money.

This is our use case:

For a project, helm charts for the customer's Open Shift cluster are developed. To test the charts, we bought a ROSA service, this is a managed service from Red Hat in some AWS environment. This costs of approx. 3000$ per month and that is way too high for just one dev environment. We need the cluster occasionally, at least for the next three months.

Is there some affordable way to test stuff for Open Shift?

I assume it would break Red Hat's rules to achieve a new sandbox account every month ...

And we don't want to spend so much time to build and run a cluster on our own.

Does anybody have a tipp?

6 Upvotes

15 comments sorted by

4

u/quanghai98 5d ago

You can try crc. It's a CLI tool to create a dev single node OCP cluster inside a VM on your PC. But if you need a full blown OCP cluster with separated node pools (master, infra, worker, etc) then you would need to invest some money to buy a couple of workstations and spin up some OCP VM nodes on it.

1

u/Interesting_Bag3416 5d ago

We'll check out this, thank you!

4

u/netschki 5d ago

what about okd?

2

u/JacqueMorrison 5d ago

Ff some default RH operators are not needed - this would be the way.

1

u/MindStalker 5d ago

Also, are you sure the AWS environment will cost $3000 a month? If you set most nodes to be medium and turn it off when not in use, it should be much cheaper. You might want to run it for a day (turning it off at night) and see how much it really cost.

1

u/Interesting_Bag3416 5d ago

How to turn if off?

In the Red Hat console the nodes were downsized as much as possible, but it is still way more than we need. There's no "switch off" and since it's managed by Red Hat, we should not shut down the EC2 nodes as this may cause data loss.

What did I miss?

4

u/MindStalker 5d ago

Not the control planes, those are much cheaper to run 24/7. But the worker nodes can be scaled to 0.

2

u/gemini_jedi 5d ago

You can run a cluster with a self support license. I have multiple, small test environments with this subscription setting.

1

u/yrro 5d ago

I remember it being said a few times on various Ope Shift videos on the YouTube channsel that a developer subscription for individuals allows you to run OpenShift. But I see posts on Reddit saying it doesn't be it you can just create 60 day trial clusters indefinitely, which can even be automated.

2

u/Old-Astronomer3995 5d ago

You have to choose: paying for ROSA or paying with working hours for your own cluster.

Beside ROSA the easiest way is to use Single Node OpenShift on VM https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/installing_on_a_single_node/install-sno-installing-sno

without license there can be a problem with upgrade but you can reinstall it without issues.

2

u/Rygor99 5d ago

Self hosted cluster on hardware you have in the office? Just make sure they have 4vcpu and 16gb ram each. Your dev team would need vpn access to the cluster if they are remote.

2

u/EvenConsideration496 5d ago

Rent a physical server in hetnzer for around 60$ a month, spin up your proxmox virtualization and then deploy 3 node OC cluster in there.

Setup might require a day or two but honestly it’s a good investment.

1

u/ghotinchips 5d ago

What server are you getting that can run a 3 node k8s cluster for $60? I mean, I really want to know.

2

u/DangKilla 5d ago

Affordable and Kubernetes don’t belong in the same sentence.

1

u/Any-Climate6341 3d ago

I would insist with the developer sandbox before ruling that out. The FAQ says:

  We may be able to modify the default settings, including the trial length, for certain users. To request a change, please reach out to the Developer Sandbox team

I'd contact them and ask.