When we started down the path of creating a Red Hat OpenShift Operator certification for partners, after a few calls it quickly came to our attention that there were a lot of moving parts that developers needed to know about prior to beginning the certification workflow.
Kubernetes Operators have been such a hot topic in the last couple years. This video discusses how to build an Operator from a Helm chart using the Operator-SDK tool. If you have a helm chart for your containerized application, follow along in my video and see how easy it is to build your own Operator!
Red Hat Tech Ready is a new virtual global technical enablement series that provides the latest in the Red Hat product strategy and enablement on the newest features, exclusive to our Red Hat internal teams and Red Hat Partners. It is a 4 week series that covers 4 different aspects of Red Hat’s Open Hybrid Cloud Strategy.
Red Hat has been publishing the Container Health Index for Red Hat images, and now the CHI will track certified partner images that include Red Hat images. This grading system will be part of the certified product listing in the Red Hat Ecosystem Catalog.
When your product is Red Hat certified, the distribution method you choose applies to two things: the repository where your images are hosted, and where your Operator will be listed and available for deployment. This article explains three options for you.
The role of the Value-Added Distributor (VAD) is often overlooked. Tech Data is a hub for new and innovative technology. We have access to lots of different vendors, platforms and skill sets. This collective knowledge informs how we manage our community and our resources
An essential phase of partner engagements is to technically align a partner’s application offering with the Red Hat platform. For containerized applications, this work focuses on adopting Red Hat’s OpenShift Container Platform.
Containers and Kubernetes play a key role for modern application development, supporting new business models around edge, IoT and AI/ML. Despite all of this, there are still some barriers to even faster adoption of enterprise open source. In EMEA specifically these center around concerns with level of support, compatibility with legacy systems and lack of internal skills.
Red Hat OpenShift 4.9 will retire a series of Beta level APIs in both alignment and support of the Kubernetes community’s goal of encouraging the use of Stable APIs to increase the trust in API usage for production workloads and meet the expectations of enterprise users.
Kubernetes has removed several APIs from version 1.22. Any Operators utilizing these deprecated APIs will not work on OpenShift 4.9+ (or any cluster vendor utilizing Kubernetes 1.22) and will block your
As the ecosystem of applications and infrastructure services on Red Hat OpenShift continues to grow, it is important to facilitate continuous testing and integration that tracks the Red Hat OpenShift life cycle.
Forrester reports that Red Hat OpenShift creates a revenue opportunity for partners up to 2.5 times the subscription revenues through implementation and ongoing management services, and building their own solutions that increase the value of Red Hat OpenShift.
In November 2021, 20 teams took part in the third edition of Red Hat Hackfest, our partner community initiative that brings partners and customers together to build innovative solutions that address complex business challenges.
Our new certification tooling allows you to run the certification tests on your own computer through the downloadable preflight tool. All you need is a Red Hat Enterprise Linux (RHEL) operating system and access to the image you want to certify.
The Kubernetes project periodically deprecates and removes APIs from the platform. Any time the Kubernetes project deprecates or removes APIs, projects using the affected APIs must adjust to accommodate these changes. OpenShift, and Red Hat partners running workloads and providing solutions for use on OpenShift, subsequently must also adopt and adjust to these upstream changes.
Red Hat OpenShift 4.11 is now generally available, incorporating many enhancements such as hosted control planes, improved pod security options, better support for air-gapped environments, deeper observability via the web console, among others.
Red Hat OpenShift 3.11 officially reached its end of maintenance support on June 30, 2022. Now that OpenShift 3 has moved into the end of the maintenance support phase – it’s time for your customers to migrate.
Combining Tetrate Service Bridge with OpenShift Container Platform (OCP), built for the hybrid cloud, allows you to run workloads virtually anywhere and abstract away cloud provider details for a completely vendor-agnostic solution.
In a previous blog post we discussed some of the general details around what customers using Red Hat OpenShift 3 need to do to migrate to Red Hat OpenShift 4. In this post, we’ll dig a little deeper into steps needed to properly complete this migration in an effective and efficient manner.
The Red Hat partner ecosystem is a catalyst for open innovation. It connects partners with a thriving network of companies, expertise, and opportunity. With Red Hat, there are multiple paths to partnership and the flexibility to adapt as your business needs change. We work to help you achieve financial success on your terms.
About Red Hat
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.