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

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: OpenShift Git Ops, Modernization Not Only for App Owners | Amazon Web Services

Description

Ryan Niksch (AWS) and Thatcher Hubbard (Red Hat) dive into the next step of evolution as they discuss the OpenShift Git Ops as a means of providing administrators and infrastructure teams the benefits application owners and DevOps teams have enjoyed for some time.

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

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

Greetings, my name is Ryan Niche I am a principal Solutions architect with Amazon web services. Joining me today is that show from Red Hat, that's just say.

B

Hi hi I'm that Robert I'm with the managed openshift black belt team at Red, Hat.

A

Thatcher I've been working quite a bit with openshift customers on AWS, more specifically managed openshift. So if you look at something like the red hat, open shift service on AWS Rosa and many of my customers are managing their application workloads, their container-based Solutions through a CI CD process, pipelines automated delivery.

A

There is a growing Trend to do operational configurations, so cluster configurations, configurations of add-ons tracking State through a similar process. What is what is Red Hat bringing to customers to help in that sort of space? Okay,.

B

Well and it starts with the git Ops operator, the red hat get Ops operator, which is an add-on of itself, uh and this is a I want to note. It is an operator which means it instantiates other instances of the the workload to actually manage various uh typically tied to a namespace but um yeah. So we start with the get Ops operator I know and that well, let's, let's start with kind of your original use case um about the get Ops operator, which is.

A

Well, before you get there, okay, under the hood of this operator, the Upstream magic of this with some secret Source attitude is, is Argo.

B

A

It is it very much Argo.

B

A

Is not at yourself managing your.

B

Own Argo, this is.

A

A packaged up, it's.

B

Argo with the integration work done by red hat and supported by Red Hat. So yes um thank you for calling that out. um So let's talk about your first use case, which is applications.

A

Yeah application, development and I think this is the bit that a lot of people are already familiar.

B

With right and that's something similar but I, do want to I just want to kind of set the stage and make sure folks get an opportunity to know precisely what it is we're talking about. So we got to get repo over here, I'm, okay, at drawing that icon um and we've got a developer or most likely a lot of developers um and they push code to this repo push it to branches. They PR it into a specific branch, and when that happens, Oregon.

A

Is going to be monitoring this and and responding to that so whenever there's a change in the repo and I'm assuming Argo would connect to openshifts API endpoint and push those configurations right.

B

Argo watches the repo it pulls, it actually uh watches the repo and when a change happens, you know that repo just holds openshift manifest. It's all. You know it's all for manipulating openshift resources, VP API, it will just apply it, and so you know if we have like a little deployment over here with a few pods in it.

B

If something changed in the deployment research in that repo Argo would go ahead, talk to the API and redeploy it just like you would maybe would manually it's. Then you don't have to do it. It's an automated process, that's managed by Argo, so yeah, that's kind of our original use case.

B

um But yes, moving on to your second use case, which is managing the cluster configuration itself um and there's a lot of things that you I guess I would say, go under day, two operations, things that are very important services that serve your developers on the cluster logging being kind of. First and foremost, thank you, Ryan.

A

B

um Vlogging is a very important one: there's a variety of things that come directly from Red Hat, uh the CSI, the secrets.

A

B

Is a very important one.

A

um If you're 20 csis there's a very broad collection of operators through the operator, third-party Solutions right monitoring, logging security right.

B

uh You know external external DNS, being you know, one sort of example, of something that's commonly deployed on an open cluster to ease and management. So.

A

This could be pretty much anything that you're able to script any any any configuration change that you're doing on the cluster or the add-ons onto the Clusters I'm going to add add-ons yeah over there. uh So if, if you could script that you could then manage that configuration through anything.

B

You can manipulate via the API, because again, what's held in these, get repoers I'm going to draw another one in here just to represent this. This would be your cluster State. It's your source of Truth for what's configured on a cluster at any time um and the same thing happens: you'd have an Argo here. These would both be instantiated and managed by the operator.

B

um Argo would pull that repo and if there was a change to one of the resources inside of it say the configuration of the logging and monitoring stack to go ahead and arbitrate that um and it would get updated. So if you were adding or changing something it's as simple, as so.

A

Two things are standing up for me: okay,.

B

A

Is this is not Upstream Argo that red hat has taken this and given customers a fully supported and added a bit of secret sauce to it yeah? The the second thing is for me personally: it's that that perspective of desired state that I have a single source of Truth. This is what my configurations are, but where this becomes more exciting to me is none of the customers. I'm working with have one openshift cluster.

B

A

They have non-production they've got production, they are hybrid, so they have on-premises they're on the cloud and they may in many cases, be hybrid Cloud users, where they're using more than one more than one Cloud. So how do we take this and and blankets apply it to say a a fleet of openshift implementations that may include self-managed openshift, as well as many manage.

B

A bunch of products uh well Red, Hat, Advanced cluster manager, is the answer to that question or the the best answer to that question. In my opinion, um in advanced cluster manager essentially extends the functionality that we're talking about here at a cluster level where you can manage, um you know you can manage the the services that run on it, not necessarily the individual apps. That's up to you too.

B

If you want to do that, you may have a reason to keep that different based on what's on the cluster, but for cluster-wide operators and configuration when a cluster gets added to Advanced cluster manager. You can have it set up, so Advanced cluster manager will instruct the cluster to install the get Ops operator and then use the same repo, because this does support a certain level of templating the same repo to do that sort of day two configuration.

B

So if you have a consistent logging and monitoring, um you know, say: you're you're forwarding, logs to cloudwatch you're on AWS you're, forwarding logs cloudwatch. Well, your cluster may be in different regions, and so that's something that you'd want to change have templated. But you do consistently want a naming scheme for the logs that could push to cloudwatch.

B

That configuration would be in your repo. You template it. When a cluster was added or a red hat ACM, it would automatically get that configuration this.

A

Is another thing I want to call out here? If you have a a net new cluster, so you've just gone through a provisioning process? You can configure Advanced cluster manager to actually install and configure the gitops operator and push configuration down, but you can also take a cluster with an existing gitops operator and.

B

A

It and and then the Rackham environment actually becomes authoritative over it right.

B

It's it is Fleet Management. That is the intent behind. It's is that it is Fleet Management and that's a really key part. We talk about policy management policies like anything else, on red hat or on ocp. Are you know it's the ammo that the API understands so so.

A

I get I get all of the benefits that developers have had with managing their application fees for my administrative or operational side of managing openshift across a fleet, irrespective of which flavor of which flavor, as well as where it exists.