4 ms·

As a freelancer focusing on k8s, and who has quite a few clients running OpenShift on-prem or outside of cloud providers, his analysis of RedHat's need for Open

As a freelancer focusing on k8s, and who has quite a few clients running OpenShift on-prem or outside of cloud providers, his analysis of RedHat's need for OpenShift shows he does not understand RedHat's biggest customers. They run OpenShift because they want Kubernetes with it's organisational advantages on-prem, while having the support they're used to. With the exception of Azure, none of the cloud providers can offer this. RedHat saw this coming, and understood that if k8s became big in the cloud-space, someone needed to address that enterpricy market. If they could get there first, AND at the same time put a second big name behind this new tech giving it more viability, it also gave them more push. But then again, the rest of the article showed the author understands very little of Kubernetes at all.

jasonrichardsmi 5y ago
https://www.infoworld.com/article/2626313/why-red-hat-should-fear-amazon-linux.html https://www.infoworld.com/article/2626313/why-red-hat-should... This was 2010, so I think I may understand better than you think.
- mohanmcgeek 5y ago
  Except you don't. Openshift started as a paas that ran on... AWS.
  - freedomben 5y ago
    Disclaimer: Former Red Hat employee working on OpenShift Correct, OpenShift has been around longer than k8s. Red Hat identified that K8s was a remarkable platform for platforms, and rewrote OpenShift on top it. OpenShift is good on clouds, but the real shine is on-prem. For anybody with on-prem hardware, OpenShift gives you an abstraction that you can use to make it indistinguishable to your users where something is running. This means you can go cloud when scaling quickly is required, and you can build the foundation on-prem where you save a ton of money. The apps won't have to change at all (as long as they're using the OpenShift abstractions rather than say an EBS storage operator that requires AWS). Considering K8s (and/or OpenShift) only in a cloud context, is a huge error that will lead one to completely miss the "why" behind why they're so important.
freedomben 5y ago
This is a personal message and off-topic for HN, but I didn't see any contact info in your profile and decided it was worth a public comment. There's a chance I'll need a freelancer to help with some (IMO fun) work that needs to be done (company info in profile). If you're interested, we should talk more. My public-ish email address is in my HN profile, although I get a ton of email there so if you email me please reply to this comment and let me know so I can look for it. Alternatively, Keybase.io (also in profile) is a good way to contact me if you already have an account (or are willing to create one).

jasonrichardsmi 5y ago

https://www.infoworld.com/article/2626313/why-red-hat-should-fear-amazon-linux.html https://www.infoworld.com/article/2626313/why-red-hat-should... This was 2010, so I think I may understand better than you think.

mohanmcgeek 5y ago
Except you don't. Openshift started as a paas that ran on... AWS.
- freedomben 5y ago
  Disclaimer: Former Red Hat employee working on OpenShift Correct, OpenShift has been around longer than k8s. Red Hat identified that K8s was a remarkable platform for platforms, and rewrote OpenShift on top it. OpenShift is good on clouds, but the real shine is on-prem. For anybody with on-prem hardware, OpenShift gives you an abstraction that you can use to make it indistinguishable to your users where something is running. This means you can go cloud when scaling quickly is required, and you can build the foundation on-prem where you save a ton of money. The apps won't have to change at all (as long as they're using the OpenShift abstractions rather than say an EBS storage operator that requires AWS). Considering K8s (and/or OpenShift) only in a cloud context, is a huge error that will lead one to completely miss the "why" behind why they're so important.

freedomben 5y ago

This is a personal message and off-topic for HN, but I didn't see any contact info in your profile and decided it was worth a public comment. There's a chance I'll need a freelancer to help with some (IMO fun) work that needs to be done (company info in profile). If you're interested, we should talk more. My public-ish email address is in my HN profile, although I get a ton of email there so if you email me please reply to this comment and let me know so I can look for it. Alternatively, Keybase.io (also in profile) is a good way to contact me if you already have an account (or are willing to create one).