\n
Building and managing an OpenShift environment yourself isn’t easy. For the customers who want to alleviate the complexity in managing the environment and focus on their applications, they can consume OpenShift as a service. Red Hat works with key cloud provider partners to deliver fully managed container environment services including two of such offerings: Red Hat OpenShift Service on AWS (ROSA), and Azure RedHat OpenShift (ARO).
\n
In previous blogs, we covered how F5 technologies (BIG-IP Container Ingress Service (CIS) and NGINX Ingress Controller) can be integrated into ROSA and ARO service offerings:
\n
\n\n
Enter our SaaS-based F5 Distributed Cloud Platform. Running F5 Distributed Cloud Mesh as an ingress and egress gateway for OpenShift, we can discover the services and make OpenShift services available in any location, be it Public Clouds, be it Private Clouds, or the edge.
\n
The second goal is to secure multiple OpenShift clusters with the following features:
\n
\n- Network policies (L3/4)
\n- Services policies (L7)
\n- Web Application and API Protection (WAAP)
\n
\n
As the result, it unifies Multi-Cloud Networking under a consistent networking policy, and application and network security, reducing complexity and providing common standards for IT pros to administer.
\n
To help users explore how to start experiencing and embracing this new Distributed Cloud model for multi-cloud OpenShift services, we are creating a series of how-to videos \"OpenShift Anywhere with F5 Distributed Cloud\", starting with the following two episodes.
\n\n
\n\n\n
\n
\n
\n
Building and managing an OpenShift environment yourself isn’t easy. For the customers who want to alleviate the complexity in managing the environment and focus on their applications, they can consume OpenShift as a service. Red Hat works with key cloud provider partners to deliver fully managed container environment services including two of such offerings: Red Hat OpenShift Service on AWS (ROSA), and Azure RedHat OpenShift (ARO).
\n
In previous blogs, we covered how F5 technologies (BIG-IP Container Ingress Service (CIS) and NGINX Ingress Controller) can be integrated into ROSA and ARO service offerings:
\n
\n
OpenShift cloud services anywhere with F5 Distributed Cloud
\n
Enter our SaaS-based F5 Distributed Cloud Platform. Running F5 Distributed Cloud Mesh as an ingress and egress gateway for OpenShift, we can discover the services and make OpenShift services available in any location, be it Public Clouds, be it Private Clouds, or the edge.
\n
The second goal is to secure multiple OpenShift clusters with the following features:
\n
\n- Network policies (L3/4)
\n- Services policies (L7)
\n- Web Application and API Protection (WAAP)
\n
\n
As the result, it unifies Multi-Cloud Networking under a consistent networking policy, and application and network security, reducing complexity and providing common standards for IT pros to administer.
\n
To help users explore how to start experiencing and embracing this new Distributed Cloud model for multi-cloud OpenShift services, we are creating a series of how-to videos \"OpenShift Anywhere with F5 Distributed Cloud\", starting with the following two episodes.
\n
Azure Red Hat OpenShift (ARO) with F5 Distributed Cloud
\n
\n
\n
Red Hat OpenShift on AWS (ROSA) with F5 Distributed Cloud
\n
\n
\n
Employee![\"F5](\"https://www.f5.com/content/dam/f5/f5-logo.svg\"){kind=logo}
