Red Hat OpenShift Red Hat OpenShift on AWS (ROSA) | Red Hat OpenShift, 19 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ROSA Introduction 101 | Amazon Web Services

Description

In this session Charlotte Fung from the Red Hat managed OpenShift Black belt team will explore the underlying architecture of the Red Hat OpenShift Service on AWS (ROSA) focusing on nodes, fuction, control and data plane as well as the relation to AWS VPC constructs.

Learn more at: https://go.aws/3CV8GBt

Subscribe:
More AWS videos - http://bit.ly/2O3zS75
More AWS events videos - http://bit.ly/316g9t4

ABOUT AWS
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers — including the fastest-growing startups, largest enterprises, and leading government agencies — are using AWS to lower costs, become more agile, and innovate faster.

#redhat #openshift #redhatopenshiftserviceonaws #rosa #AWS #AmazonWebServices #CloudComputing

A

Hi, my name is Charlotte Fong and I am a cloud services. Black belt, a red hat today, I'll be talking to you about red hat openshift service on AWS commonly known as Rosa.

A

So what is Rosa Rosa is a fully managed jointly engineered product by red hat and AWS, which gives you a kubernetes ready platform where you can run your applications, but for today, I'll be talking about the fundamental architecture of Rosa, which is like the simplest architecture you can think of so because Rosa runs um in AWS, you get. Your cluster will run in a VPC.

A

All right and for the fundamentals, like the simplest deployment of a Rosa cluster, it will be a single easy deployment.

A

A

We have your single, easy and I just want to point out. This is the simplest um default architecture for a new user. That's trying to understand what Rosa is and to get started for the fundamental default deployment we need to subnets.

A

One would be a public supplement.

A

And the second subnet will be a private supplement.

A

So what happens is all your cluster resources will be in your private subnet and in the public subnet you're, going to have your uh egress and egress resources so for each cluster? Each cluster is deployed with three control note.

A

At least three- and this is to account for resiliency and high availability, each control node comes with an API server.

A

A

And with the controller.

A

We also get two infrastructure nodes, a minimum of two infrastructure nodes and also this is to account for resiliency.

A

And each infrastructure node contains uh an inbuilt registry.

A

uh We also has a router layer, and it also comes with the monitoring server.

A

And also for each cluster, you'll get at least two Walker notes.

A

Which is where all your applications will be running on so worker times, two.

A

In four times, two.

A

A

So this basically is um like your open shape your Rosa resources, which will be located in your private supplement for this resources to communicate with the internet. You can make use of a not Gateway which sits in your public subnet.

A

So now you may Wonder, how do you get access to the cluster in the private supplement? So Rosa comes with pre-built load, balancers and I'm going to be talking about them right now.

A

So let's assume um this is a developer.

A

Or even a SRE, which is outside reliability, engineer that support browser that manage the cluster for you so for default deployment both will access your cluster through the internet.

A

And they'll make use of a series of load balancers that come pre-built with your cluster, so the first load balancer.

A

Will be your external internal API, Network load balancers that gives access to your control plane.

A

The second load balancer.

A

We call this the SRE um API elastic load balancer, and this is what a SRE team used to manage your cluster.

A

For end user application access, we will make use of.

A

um An external internal elastic load, balancer.

A

And this will talk directly with your router layer on the infrastructure note and we also have a full load balancer for SRE console access.

A

And this also communicates and SRE also use. They use that to manage your cluster internally. Your clusters would communicate with each other.

A

Using the internal Network load balancer, so from a fundamental perspective, this is what your cluster will look like, but we do not recommend this for a production, um great deployment for production. We highly recommend that you use a multi-az deployment where you're going to have three control planes in each AZ, um three uh infra notes in each. You have three control plane, one in each AZ, three in front notes, one in each easy and at least three.

A

What cannotes one is each easy which helps you to make use of high availability, High resiliency of the AWS cloud.