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

Previous Meeting

⏯

youtube image

►

From YouTube: Red Hat Providing Value through OpenShift and Developer Experience Tools | Amazon Web Services

Description

Ryan Niksch (AWS) and Shaozen Ding (Red Hat) discuss the value of OpenShift as an application platform for developers and application owners, and take a look at add ons which can compliment the developer and administrator experience.

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

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 Nicks I'm, a principal Solutions architect with Amazon web services. Joining me here today is Xiao Jin from Red Hat shouting, say.

B

Hi hi I'm, Sharingan I'm, a right ahead manager, service, black belt and.

A

Today, I'm gonna pick a fight because I want to talk about how red hat open shift is kubernetes and I. Don't think that's important, and before you get excited, let me tell you why we commonly talk about open shift, whether that is self-managed, ocp or whether that is a managed service such as Rosa, and when we're engaging with people. We talk about how this is Enterprise kubernetes. This is kubernetes, it can be run at scale and everybody fixates on.

A

The kubernetes layer of openshot, if we compare openshift to other kubernetes products, let's compare it to like native kubernetes as an example or a DIY, kubernetes environment. We end up comparing open shift gist of the kubernetes layer and and I feel that that doesn't do justice to openshift. There is so much more here immediately what I want to draw attention to is yes, there's kubernetes, fantastic, that's great for container orchestration. There is a run time under the hood that I think openshift does a very good job of abstracting.

A

The complexity away from the container runtime yeah I feel openshift also does a really great job of extracting away the the real nuts and bolts of kubernetes I don't need to be in kubernetes expert to use open shift, which, which might be a little bit different for something like native kubernetes but there's stuff on top here.

A

Bold pipeline processes, logging monitoring security, let's spend a second and just zoom in on those and then what I want you to do is run me through what are the things that red hat is providing developers in terms of productivity and experience that are not necessarily coming from openshift itself, other components and complementary add-ons yeah that really make a difference. So we've got the kubernetes layer.

A

We've got the container run time over here, so there is a a run time, but then we've got sitting on top of this and I'm just going to add some of the things that are standing out. For me, there is a build there's a pipeline process there is deploy and there is monitoring and logging super important to all of our customers. There is security across the board and I find openshift is a little bit more prescriptive in its security model.

A

It's not just the case that the customer can turn things on and then I'm just having the knobs and dials. There is actual recommendation in terms of the security day. What else am I forget missing? That is open shift out of the box. I think options.

B

um Yeah so let's talk about like a little bit on developer experience or inner loop experience. So there's a product called um open shift, Dev spaces.

A

This is the the older con container workspaces, yes, okay, yeah, so, and- and this is a developer IDE where, if I'm a developer and I don't have a laptop or I, don't have something I can literally log in from anywhere and have my environment yeah. So for me this is fantastic, because if my laptop dies, I I, don't end up dead in the water, I can literally find any system connect to my openshift Dev space and continue working. Yes,.

B

Yes, like it's, it's just trying to improve the inner loop of developer experience. Have you heard about inner loop, I haven't tell me a little bit.

A

B

It yeah so like uh the dev space is trying to give you just a application. uh Jessica workspace part and the developer can actually, you know, do all the things within the inner loop.

B

It's including develop the code test, the code and deploy the code to openshift or lose them, and so they can finish all this kind of like code, editing, testing the whole cycle, and then they can commute the code, for example, to a GitHub repo, and then you know the the pipeline and to pick up the the from the GitHub repo and then enter the production deployment. So this.

A

Is really my open shift environment shrunk down into a developer local environment, where I can run through a similar experience, but without needing to deploy all of the infrastructure of openshift itself?.

B

A

Then, taking the next step that once I'm ready for there I can actually bring it into my openshift environment through a CI CD pipeline yeah. So.

B

We have another two products right, so openshift Dev space is for developers. Inner loop experience for pipeline building openshift provides another Open Source Products, which is called openshift Pipelines.

B

A

Pipelines when, when I think of pipelines, I immediately think of like Ci CD processes in openshift of old, that was uh stereotypically like a Jenkins type platform. This is tecton and I. Think Argo CD as well under the hood. So.

B

Yeah Argos, it is branded as another product is called openshift githubs.

B

Right so tecton is a very popular Open, Source Products. It's trying to build a building blocks for our pipelines. It's it's not like Jenkins, because all the tactile processes actually won as a kubernetes part. So you have a lovely elastic Advantage by using tecton and the other thing so Tech tongue is a pipelines right. So it's for a CI process right. You can use this to create a customizable, composable, um CI building blocks and then for the build. Ops is based on Argo CD.

B

Is focus on the continuous delivery process? You basically, you know you have GitHub, has a declarative of your application in Manifesto way uh to describe your application and Argo City is able to reconcile this to the openshift cluster. So you can see we have this interloop experience to uh for developer to Code test and deploy their own application within a pod.

B

And then you have pipelines actually building all the CI process as native kubernetes, and then you can use githubs to um to actually deploy to various environments and even um promote the environments right, for example, from staging to production.

A

I think we're missing something here uh when we talk about pipelines and in the CI CD process to store the objects created by the build and pipeline process. I think clay should come into the picture here somewhere.

B

Yeah um you, where you'll build the pipelines right, so there are multiple process right and uh you won't build pipelines. For example, you probably um do the union test first and do some code analysis or scanning, and if you like, building Java stuff, you have a release cycle. You may need a artifactory right and the next step is you're going to build image.

B

The building image- you definitely need a image registry, luckily, like openshift itself provide internal registry. Yes,.

A

B

A lot of customers they prefer to using their existing or externalized registry. That.

A

Could be AWS ECR, it could be redhead Quay. There's a lot of different options over here. Yeah.

B

uh Ecr right.

A

B

A

B

Are a lot of options? Darker registry? You know all these kind of things.

A

You mentioned over here a scanning and when you say scanning, I, think of scanning in two ways: um sort of static content scanning code level scanning, uh but then there's also scanning of the typical container objects and now I'm thinking security tools like Aqua security, sneak um Prisma, these all hook into this process, and they all have a very close partnership with both AWS and and red hat, and they become instrumental in this part of the process. Here.

A

um The other thing that I'm curious about is as you're going through this sort of flow. If we look at open shifts abstractions- and we look at something like.

A

Sourced image, s2i yeah does a customer or a developer using source to image where they're just writing code uh bypass some of the inner loop experience or bypass some of this.

B

Yeah, so um the first two image is one way of to build your image right. So, as you mentioned, there's abstraction. So when you build the image source to image, is what openshift provided based on you know. They have a very a good abstraction of container, and then you can pull that container and run through the build process for different kind of code framework. For example, Java go land, those kind of stuff I.

A

Think the real benefit for me for source to image is as a developer or I'm, focusing on what I'm really good at what is important to me. I'm writing my application code. I'm not overly concerned about building containers. Openshift. Does that for me yeah, which becomes an acceleration Factor, yeah and.

B

It also has a benefit for operator to standardize. You know the security image because source to image you, it has a base image, so that can like actually make sure the base image is cured is standardized everyone using the same thing to build Java. Everyone is using the same thing same base image for Golan those times.

A

Now those Bass images, those are maintained by Red Hat they're, patched by Red Hat. They are validated from a security perspective exactly so the same benefit I get from a trusted operating system like Rel or core OS is now applying to the containers as well. What I like about this is when I think of openshift I tend to think of it from a infrastructure perspective and I'm getting all of this. But there really is a lot more developer-centric benefits to openshift. It's not just a kubernetes orchestration platform.

A

It really is a comprehensive developer experience and the intent is to accelerate my business at every single step of the process and and for me, openshift 4 has done a really good job of moving away from not just providing benefit to developers or application owners, but really to those operations, teams and and sort of CIS admins in the back end that are managing the infrastructure side. So it's become a very much more, uh encompassing inclusive benefit that provides overall business benefit. Yeah.

B

Kubernetes to me is is kind of like a container scheduler right, but on top of that you have operational. Like you mentioned, observability monitoring logging. You know, then we have developer experience. As you said, openshift is uh it's beyond just kubernetes.

A

Yeah I see it as a turnkey solution that brings everything that my business needs yeah in one box charging. Thank you very much for joining me as always a pleasure having you here. Thank you and thank you for joining us.