Red Hat OpenShift Detroit 2022 OpenShift Commons Gathering, 25 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Lightning Talk: RHODA Service Update - Raghuram Banda - Red Hat OpenShift Commons 2022 Detroit

Description

Lightning Talk: Red Hat OpenShift Database Access (RHODA) Service Update
Red Hat OpenShift Commons 2022 @ Kubecon/NA
Detroit, Michigan
October 25, 2022

Speaker:
Raghuram Banda (Red Hat)

https://commons.openshift.org/gatherings/kubecon-22-oct-25/

https://access.redhat.com/documentation/en-us/red_hat_openshift_database_access/1/html-single/quick_start_guide/index

A

A

I work as a solution architect at Red Hat today. The topic is: how do we simplify access to the databases that are managed databases in the cloud? If we take a quick look at the agenda, we look at the industry Trends and then we look at some of the challenges that customers May face and then we present what red hat offers as a solution to them. And then we take a quick look like a walkthrough at the solution and then we can also share some references if you would like to try.

A

So let's get started now the slide that you're seeing here. So this is the data that comes from a survey, so that's done with more than 200 contributors and they're across emea, North, America and then Apec, and they come from different Industries like FSI, Telco and other Industries, and also the personas of the different people who are involved. Some of them are directors vice president and then csos, so so what this means?

A

Basically, as you see on the top, you know the top workloads that are deployed on openshift are the kubernetes platform, are database and AIML related. So this is the data that came after the survey now.

A

That brings us to the question right. So why deploy you know, databases and data analytics workloads on openshift?

A

So if you look at here so with openshift being the Enterprise kubernetes platform, uh it helps the automated operations, for example, the flexibility it offers while using operators, and then you could use Helm, chats or customize to deploy your applications and when it comes to consistency and portability, which means you can deploy your applications all the way from on-prem to cloud and also you will be able to migrate your applications easily across multiple environments and, of course, redhead has strong Partnerships with different vendors.

A

In this context now this is a interesting slide which I want to share from my own experience. So back in the days we wanted to migrate, some applications from on-prem to cloud and one of the applications we needed to connect to a database at the time we were also dealing with AWS. So there is an initiative going on and they said hey. You know what you can use some of the services in AWS, so one of our developers they have identified RDS and said you know we would like to connect to RDS for our application.

A

So well at that time. You know in in in in the involvement that I've been in. Like you know, I was like somewhere in Atlanta, like almost on vacation. I get a ping from my developer, saying: I need access to AWS and then for me the first thing is sure, and- and why do you need that? He says I need to create a database right now. I always keep these things in mind when it comes to security. So the first thing I was like okay. How do I share the credentials?

A

Of course I don't want to share them over chat or something, but then also there is a lot around. How do you do the automation like do? We need some scripting and then also there can be some inconsistency which means in this case, for instance, we also want to deploy the same application, but on Azure with a different database. So that's also a question around. You know how are the user interface looking like for these different services that are offered within the cloud, so this also gives some opportunity for errors so to put in perspective.

A

This is a lack of productivity and, of course, at that time like when I was thinking about these things.

A

Obviously, my developer was frustrated because he's waiting on me so and also from a secops perspective right, if you have a different team, they're totally unaware of what is happening, which means, if you, if you create a database in the cloud and if they don't have visibility to it unless they go and check in or unless they have their own mechanisms, they wouldn't be able to see that so so that creates some limitations on the visibility aspect, so in that sense there is also corporate risk right.

A

So these are the uh you know: situations when it comes to the current scenario when they are not using uh something like this now. How does this challenges of ad hoc database uh are looking in the Enterprise? So, just to repeat, uh it won't provide a central visibility uh when it comes to the areas across the application, usage or audit, and then, when it comes to sharing the data, if it involves credentials, that's a huge challenge.

A

Right now also the usage it can be unconstrained and also there can be some redundant instances, especially when we have more than one developer working in a team and if they're trying to work on the same user story. So there could be some scenarios. uh You know where some effort is duplicated right now. How do we solve this, like? What's the red Hat's approach to solve this problem, so we introduced redhead openshift database access.

A

So with this, it's going to simplify the ability to provision connect and also monitor the developer, access for the databases that are hosted in the cloud like managed databases, and also it's possible to have this even in multi-cloud and hybrid Cloud environments.

A

Now, when you look at the managed cloud services from a red hat perspective, when you look at this picture as to understand where Rhoda fits into the architecture, so as you see this on the bottom, uh we have this hybrid Cloud flexibility, which means you can have this multiple Cloud providers, be it Amazon, Azure or IBM Cloud, so different Cloud providers. And then, if you see on top of it, you have this different services. For example, when it comes to Azure, you have Azure Reddit openshift as a managed service and then Amazon you have Rosa.

A

So in the same way, you have other services now, on top of it, where the value of openshift is realized, you have openshift data foundations coming in, so this is how it fits, and then, if you recollect what I said just before on slide 5 around the scenario, like the current scenario now we would like to show how this will address those which means um by having openshift database access. You would have self-service, which means you have the self-service access to the databases of database Services, which means it enables autonomy for the developers.

A

And then you also have a user interface that will be provided within openshift to have some visibility and also you have the apis when it comes to programmatically, interacting and then also it doesn't have a need for a lot of skills like you, don't need to involve a lot of upskilling and, of course, the operations is going to be happy, because you know they can understand how they can grant Access Control to the developers or they can get a lot of visibility, and it's easy to maintain so so.

A

This is how the redhead openshift database access will solve those issues, and you know present a good um scenario now, if you look at this, what this means is this is providing an access path, so Rhoda plays a role in providing an access path while trying to connect to the different databases, which are the managed databases. And then, if you see you have RDS mongodb crunchy on the right, so the list keeps growing, which means the the product team continues to evolve. The list of the databases that can be supported.

A

Now, if you look at, you know how this will make an impact on the different teams or the personas. So when it comes to the it operations, it makes sure that it's establishing consistency so which means what they always look for. You know, which is the standardization and governance, so it is established and for developer. It improves the agility, which means the self-serve self-service ability is improved there and then, when it comes to the DBS, they have much more control and much more visibility.

A

So so this is how it makes an impact on the different areas within the company. Now, having said that, I just want to do a quick, walk through and just explain how this solution looks like.

A

So what you're seeing right now this is a hybrid Cloud uh console from Red Hat. So in this case, I can show you by showing my cluster, in this case I'm using a red hat openshift cluster on op Amazon.

A

Let me bring that up. So if you go to the hybrid Cloud console, uh this is where I have my cluster. Assuming that I have created a cluster when I go here, I have a tab called add-ons and then I get to choose or click on redhead openshift database access and when I click on install this will take care of making sure this is installed on the cluster.

A

So this is how it works when it comes to the browser- and you will have a similar experience with another openshift cluster on the cloud now, what this means is. Basically, this will take some time so in the interest of time, I want to show you how this looks like in the openshift cluster. So so, when I go to the open shift and when I go to the install operators, this will be installed as a operator on the openshift cluster.

A

So, as you see here once the install is completed, you would be able to go to your operator Hub and you can see the loader operator installed now what this means. This can be done by an admin in a case where you have teams, with operations or with with different teams, doing a different team, different things from an infrastructure and active site, but in general you know, anyone who has access to the cluster with admin rights can come and see here now.

A

This is uh this: is the operator part of it and what this means is? You will get a new entry item on the menu on the left side. If you go here, you'll have data services and when I click on database access, so this provides a single pane of view. Like One Stop Shop remember, we talked about visibility as to understanding the instances and then the different databases that the applications are trying to interact. So this is where you get to see them now for today's purpose.

A

From a developer perspective, I want to take an example called fruit shop, so in this case I'm not doing the CI part but I'm, assuming that I have an image built and pushed to a container registry which is called fruit shop now.

A

The good part here is, let me show you this repository, so, as you may know, you may use something called a Helm chat to deploy the application, and if we are speaking about a team who is already doing git Ops, which means the ability to use git as source of Truth and have your kubernetes or openshift manifest in the git repository. So in this case, Rhoda provides you the flexibility to have your manifest declared in the git repository.

A

So what this means is, if I'm a developer, if I'm trying to connect my application to one of the managed databases, I will be able to declaratively specify all this manifests, and this is an example of the Manifest that are involved and I'm using Argo CD in this case. So if I go here, so this is my Argo CV application, so just to quickly explain so.

A

This is basically using the git repository, which I just showed as an example to get those manifests and once we create the application and once it is sync, all these manifests are created and the best way to check is by just going to the once. The sync is finished, as you see here, it says sync: okay and now I could do it like I could scale replicas and do a sync again but again to save some time. I will go and show you like how to verify. So this is the developer console.

A

So when I go to the developer, console I would see. uh So in this case, I have created a namespace or project called openshift, Commons Rhoda. So as you see here, so this is the application itself that is deployed, and then this is the connector like. If you see this is a service binding that is uh helping us to connect the application to the database. Now, if I, just click on this, this would be the route to take me to the fruit shop application. So this is a rest.

A

Api I could query by doing a get call, but in this case I would go to the UI. So in this case I'm just just to test. If my application is working or not, I would add a fruit. So I can add something called mango as a fruit.

A

And if I save it yeah, it's saved, so so, just to summarize what we have seen so far, so we have seen how the operators installed uh when it comes to using something like Rosa and then we have seen how it looks in the operator Hub and after that we also have seen that you know we can actually deploy or configure the application to connect to database in a github's way, and this is all we could achieve and what we can go further is also if we are thinking about implementing cicd pipelines like using openshift CI CD.

A

We could also use this code and Implement our pipelines, so that's about how the demo or the application works while using Rhoda. Now, if I go back to my presentation, so this is the roadmap kind of understanding where the product is right now. So, if you look at fault, 22 it's in service preview and we are working with some of the customers who would like to use Rhoda, and you know we can always help if anyone is interested to try the product and there are some resources on getting started.

A

I can share this slides later, but you can look at here as well on how to do, and these are some of the resources, like blog posts, just to give more knowledge on Rhoda and other examples. That's it. Thank you. Thank you for taking the time to listen to me. Thank you.