As we approach the end of another year for Red Hat OpenShift and Kubernetes, and another Kubecon, which I believe will be even bigger than the last, it’s a great time to reflect on both where we’ve been and where we’re going. In this blog I will look back over the past 4+ years since Red Hat first got involved in the Kubernetes project, where we have focused our contributions and the key decisions that got us to this point. Then in Part II, I will look ahead at some of the areas we’re focusing on now and into the future.
OpenShift is a leading enterprise Kubernetes container platform. With hundreds of customers, spanning industry verticals, and deployed in enterprise data centers and across major public clouds, OpenShift is enabling customers to evolve their applications, infrastructure and ultimately their business. While OpenShift itself has been around since 2011, it was the decision to standardize on Kubernetes in 2014 that changed the game for OpenShift and for Red Hat as a whole.
OpenShift 3.0 would launch a year later in June 2015 and it was built on 3 key pillars: These 3 pillars still form the foundation for OpenShift today, but bringing Kubernetes to the enterprise required more. Enterprises typically have complex requirements around security, interoperability, compatibility and more and they need a platform for both building new cloud-native applications and modernizing existing applications and services. In the last 4+ years Red Hat has invested to build new capabilities, both in Kubernetes and around Kubernetes, driven by the needs of our customers and the community.
In the past I’ve written about why Red Hat chose Kubernetes, so here I’d like to highlight areas of Kubernetes where the OpenShift team has invested, why they’re important, and then look ahead to what comes next.
Source: openshift.com