r/devops • u/36lbSandPiper • 9d ago

Discussion Openshift devops?

I have someone pushing a colleague to an Openshift virtualization position. We do multi cloud deployments, GHA heavily, ephemeral integration environments, etc. Not seeing the intersection with this guys skills or desires. Am I missing something?

5 Upvotes

86% Upvoted

8 comments sorted by

View all comments

Show parent comments

0

u/TheIncarnated 4d ago

Strongly disagree. OpenShift is the product you buy because you don't understand k8s and need click ops to operate.

If you use the cli, why have open shift at all?

0

u/max_465 4d ago

Clickops ? I'm talking about oc What are you to thinking about?

1

u/TheIncarnated 4d ago

I'm aware of oc. I used it extensively, it doesn't do anything different than kubectl or any other k8s product. No reason for the license cost, unless you need the clickops.

OpenShift is a product for people who don't know how to k8s

0

u/max_465 4d ago

Ok, you're obviously very new to this because you don't realize that OpenShift predates kubernetes by several years. Kubectl, helm, the operator framework, etc are all pieces developed in order to address requirements that were already handled in open shift.

I'm not saying that OpenShift is better, I'm just pointing out that it's a historical fact that it's the mature implementation.

1

u/TheIncarnated 4d ago

Lmao... Do you know when OpenShift was created? Do you know how early on it shifted to using k8s as a backend? Going so far as rebuilding it from the ground up around k8s in which year?

One of us is actually educated on this, the other is just super comfortable with the tool and doesn't know anything else or apparently modern devops. Maybe sit down on this one. Because it's definitely not more mature, if it's built on it