Choosing betweeen managed kubernetes (AWS EKS) vs OpenShift or Rancher for large enterprises

DevOps Kubernetes
1

I have a very generic question, I have my opinion but I’d like to hear yours.

What’s “the best” choice between a (partially) ‘managed’ cloud solution like AWS EKS and an indipendent “product”, based on ‘vanilla’ k8s, like OpenShift or Rancher, for a large enterprise having the know-how to manage both?
I’m more comfortable with a “product”, offering a tested platform with a tested set of addons and a paid support.
I consider DIY and partially-DIY solutions like EKS like not suitable for a large enterprise: I hate mantaining Terraform/CloudFormation code and similar craftsmanship.
But I know also that EKS is widespread adopted.

Is the original dream of Kubernetes as abstract “layer” to isolate from cloud provider definitely dead?

2

TBH I prefer a platform that I could have the control of what is happening under the hood. So, in your case I choose openshift, kubeadm, etc.

3

Large enterprise usually have own hardware and experienced staff. So choosing bare-metal k8s looks like good idea

4

EKS (and other clouds) is a good solution for variable workloads such as online marketplaces, gaming platforms, marketing campaigns, etc . The cloud allows us to use autoscaling features to withstand extreme load during the peak periods and save money during calm

5

no, we already are on AWS

6

Own hardware (+ maintenance + power + Internet + IP addresses) can be more expensive than AWS. You must have strong reasons for migration

7

we just ended our migration to the cloud.

8

Your question about choice between EKS and VMs with rancher/openshift?

9

actually we have Kubernetes clusters running on EC2s

10

a commercial distro, essentially, “vanilla” k8s + many products

11

but we need to change

12

I prefer EKS in this case.
Amazon have good expertise and toolset

13

I don’t like much that EKS is “only” a managed control-plane and some basic add-ons, everything else is up to you.

14

I think it depends on personal preferences

15

of course.
thank you for your replies

16

PS I recommend to look https://github.com/aws-quickstart/cdk-eks-blueprints
This framework allow to install addons very easy https://aws-quickstart.github.io/cdk-eks-blueprints/addons/ by declare in the .ts file like this:

const addOns: Array<blueprints.ClusterAddOn> = [
//    new blueprints.addons.ArgoCDAddOn,
//    new blueprints.addons.CalicoOperatorAddOn,
//    new blueprints.addons.MetricsServerAddOn,
//    new blueprints.addons.ClusterAutoScalerAddOn,
//    new blueprints.addons.ContainerInsightsAddOn,
//    new blueprints.addons.XrayAddOn(),
    new blueprints.addons.AwsLoadBalancerControllerAddOn(),
    new blueprints.addons.VpcCniAddOn(),
    new blueprints.addons.CoreDnsAddOn(),
    new blueprints.addons.KubeProxyAddOn(),
    new blueprints.addons.EbsCsiDriverAddOn()
];```


This product is a useful "wrapper" for cloudformation
17

As seasoned sysadmin, I would prefer a “product” tested and supported as a whole.
If a lot of large companies choose expensive products like OpenShift, perhaps there is some reason.

18

There are also managed service providers like <https://www.giantswarm.io/|Giant Swarm>, which will manage your Vanilla Kubernetes for you.
No longer affiliated with the company, but they are excellent professionals and the best people you will ever meet.

19

Cloud does not have to be always good option, you can save a lot of money with your own hardware
https://world.hey.com/dhh/the-big-cloud-exit-faq-20274010|https://world.hey.com/dhh/the-big-cloud-exit-faq-20274010

20

I know and I fully agree but its only my personal opinion as actually my company has just ended its journey to the cloud.