Red Hat OpenShift GitOps Guide to the Galaxy | Red Hat Livestreaming, 16 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitOps Guide to the Galaxy (Ep 29) | GitOps Top 10 for 2021

Description

What are the top 10 GitOps topics for 2021? In this episode, we count down our hottest GitOps topics of the year and discuss what's coming next. We'll take a look back at highlights on Sync Waves, Helm, ApplicationSets, DevSecOps, GitOps Con, ArgoCon, and more. So don’t miss this episode and join host Christian Hernandez for a rundown of what's important to GitOps and what we should take into 2022.

Follow us:
Christian Hernandez https://twitter.com/christianh814
Alex Collins https://twitter.com/alex_e_collins

What is GitOps Guide to the Galaxy?
Every other Thursday at 3pm ET hosts Christian Hernandez and Chris Short sit down to discuss everything in the GitOps universe, from end-to-end CICD pipelines to creating Git workflows.

Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1

About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
Openshift.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk

#RedHat #GitOps #Kubernetes

A

A

B

Good morning good afternoon good evening and welcome to another episode working on openshift.

A

Everybody has something that they need on top of the red hat portfolio.

B

All right and we are live so welcome everyone to get off sky to the galaxy. I am I'll, be your captain on this journey. Christian hernandez, technical marketing here at red hat and again you guys out there watching are my co-captain for this journey, and um first I'd like to call out that. uh Thank you for the fine folks at midnio uh for giving me this shirt. I actually got to say kubecon.

B

I actually really like this shirt, I really like mineio um and it realized I haven't worn it yet so I'm wearing it now and still kind of still buzzing from kubecon, because um registration's open for kubecon eu 2022. So that's uh that's exciting um and yeah. So this is the last episode of the year right we're going to take a break right. We did this last year we um uh we took a break around this time.

B

For those that you don't know, red hat. Does this recharge days and um one of the recharge days is actually a recharge week. um We take the week off I'm going on pto around this recharge time, so I'm going to take some time off, um I'm pretty sure. Hopefully, all of you out there are taking plenty time off. I know burnout's pretty real so um and I thought maybe this year you know I've worked with. um You know uh producer stephanie who's.

B

In the background there uh worked with her and decided to do something new, maybe something a little fun, something I haven't done before, we'll try it out we'll see how it works. um I decided to do a like a year recap or a year review, and I decided to do kind of like a top 10 right, the top 10 coolest things that have happened um in the world of get ops this year in uh 2021. So um I have 10 things right.

B

We have, we have uh sort of a clip, show going on right, it'll be really cool, so I'm going to get right to it, uh because we have a lot to get to right. So um all right so here coming in at number 10 is episode. 7, right episode, 7, where we talked about sync waves and hooks with argo cd.

B

Sync waves and hooks right, so sync waves and hooks. So this is what I like to call controlling non-declarative things. Declaratively right question is: um how does this work right so like you're yeah, if you're, watching, if you're watching this? It's like? Okay, all right? So how do I put this together? So um so? First, when argo starts a sync, it orders the resources in a particular way right. So first it'll order them by phase right. So it'll take all your manifest and okay it'll. Look at it.

B

Okay, I'm gonna, put all the precincts in one batch. I'm gonna put all the sinks in another batch and I'm going to put um the postsync in another batch right so once it does that so it'll sort them that way and then within each phase, it'll sort them by the way that they're in right, so it'll start from the lowest number and then it'll apply it going to the highest number in the precinct.

B

All right, um there's some technical difficulties right we're going to try that again. We'll do that again. This aws thing. I think it's really messing everyone up, so we'll try it again. Number 10 sync waves with argo cd.

B

Nope, I think we'll have technical difficulties again. Bear with us.

B

B

All right for those who just joined, I see some people coming on we're going through the top ten we're having some technical difficulties. uh We're trying to get these these clips. uh You know clip shows it's the first time we're doing this. So it's it's a little um uh um uh we're trying to figure out how to move the things back and forth, and I know a lot.

B

People are having issues uh because aws thing I don't know about you, but I'm pretty sure I'm ready for this for this year to be over, so we can all reset. um Here we go.

B

We're gonna take a really quick short break figure. This out we'll be right back.

B

B

B

B

B

B

B

All right all right, so we are back, I'm gonna! Try it again all right. Let's we're we're in this together right we're in this journey together um all right, ready, number 10. number 10 we're going to do um episode, 7, sync waves and hooks with argo cd.

B

Sink waves and hooks right so sink waves and hooks. So this is um what I like to call orders or restored on that one. What I like to call controlling non-dick.

B

All right, we got all the kinks out, yet there we go um one second.

B

There we go sync waves and hooks right, so sync waves and hooks. So this is um what I like to call controlling non-declarative things. Declaratively right question is: um how does this work right so like you're yeah, if you're, watching, if you're watching this? It's like? Okay, all right? So how do I put this together? So um so? First, when argo starts a sync, it orders the resources in a particular way right. So first it'll order them by phase right. So it'll take all your manifest and okay it'll. Look at it.

B

Okay, I'm going to put all the precincts in one batch, I'm going to put all the sinks in another batch and I'm going to put um the postsync in another batch right so once it does that so it'll sort them that way and then within each phase, it'll sort them by the way that they're in right, so it'll start from the lowest number and then it'll apply it going to the highest number in the precinct and then it'll do that for the sink and then so that's how I'll order the ammo.

B

All right so number 10 was sink waves and hooks, what's really cool about sink waves and hooks. What were my favorite thing about sink waves and hooks is that um it gives you the ability to order things right and for not everything is cloud native ready day one and, like I kind of um put in the clip you know, you'll be able to order your um your your manifests. You know zero one, two three, because not everything's ready, not everything's, declarative and that's what's really cool is that you can start your declarative journey.

B

Your good ops journey with sync waves already built in to argo cd and by extension, openshift get ops, so really really cool. um With that we're going straight on to number nine right um number: nine episode, 11 working with helm.

B

You know, helmet was a way to um uh you, know, define a a set of, uh I guess, manifests in a um in a predictable manner, right in a release. Manner right, so it's like okay! I have these manifests that have that, provide this functionality um and there's an order that we need to follow and yeah all that fun stuff, yeah, all that all that fun, stuff, right and so helm um was a way to install things essentially.

B

So when I first started working with helm and I think a lot of people um when they first started working helm version 2, it was, um they were a little nervous right about using tiller and um and being able to use helm, which is a lot of people, especially here at red hat, um especially using openshift. They used um openshift templates instead of helm, but now um helm version three.

B

You know we're here at red hat, we're all in on helm, v3, it's the packet manager, first class citizen on openshift and also supported on argo cd. So you can use still use your your helm templates right if you're using helm, you're able to use helm just fine and you can integrate that now with argo cd and make them get up friendly. So um so that was number nine. We I love helm now I use helm exclusively um so moving right along number. Eight is episode, 15 introducing the app of apps and application sets.

B

So this is application. Sets.

B

And so I got application set, so the idea with the application set is essentially a um a graduation or a a a uh the next iteration of what application sets were they're, just like all right, let's, since everyone's doing application sets and these helm charts, let's kind of um mix these things together right, let's actually just make this a thing, so they call that an application set, so an application set is nothing more than I would like to say an application factory right. So you you give it.

B

You know um one of the engineers uh I was talking to one of the engineers. Our grocery engineers I said yeah application set, is nothing more than you give it. This application set resource, it goes burr and then a bunch of applications come out right. So it's kind of like a like a you know. It's like.

A

Sound effects and everything yeah sound effects, money counter going yeah.

C

Yeah money counter going.

B

And it spits out applications right. So it's it's! um It's a simple. It's essentially a templating agent to create applications.

B

So um that kind of brought a smile to my face, because I remember that episode um part of this also reminds me of chris, and you know chris wherever you are um well, we know where you are you're at aws. Doing great things um we miss you here so um so yeah application sets is essentially, people were taking um app of apps right. They were creating an application that had many applications, so um I think it was a great great call by the engineers like hey.

B

Let's actually make this a real thing: it's making it um making deploying applications even easier than it already was on um using argo cd on openshift. So that's. This is really really cool. um It's very inception like in which what I really like so so cool number seven episode, 20 multi-cluster management with acm, moving beyond getups.

A

Advanced cluster management had a way of provisioning, apps and doing github and helm. You know which do I use. Do I use argo? Do I use the acm subscriptions? You know, how do I make the choice, and you know the answer used to be well depended what you were doing. That answer is still the same. It depends on what you're doing, but in both cases we want you to use both.

A

We want you to use them together, and what we're going to show you today is how acm and argo are like this they're fully integrated the acm brings the fleet management that was sort of lacking from the argo space. Argo is very much the you know contained for the the cluster that it's working on or if you've gone out, and you have a bunch of clusters, you still have to bring those in acm.

A

We're gonna see, brings all those pieces together and gives you that that visibility into argo that one number one we never had before, but number two allows you to operate. Argo and through openshift get offs at scale across the fleet, and so you know, as christian mentioned, you know doing everything from day zero on through day infinity with your cluster. um I, if those of you familiar with acm, I just navigated in from the welcome screen down to applications, and so what we see here, you see some type, some labels that say argo.

A

We see some that don't have it, I'm not going to get into that just yet. What I want to talk a target on here is: there's this application, that's deployed in acm, called infrastructure build out, and so the back story in this is that I got an open shift cluster. I ran an open shift, install to be honest internally. I just requested one and it came up, but you deploy an open shift cluster you go to hub, so you go into openshift's uh operator hub.

A

You say I want acm, you hit the install button in seven minutes. You have an acm cluster at this point, I'm at this stage I have no applications. I have no other clusters. I want to create my first application in acm, and so I go through. I click the create and what I do is I choose get, and I pick my infrastructure git repo and in this case it's labeled get ops fleet samples.

A

So I pick my repo that has all the definitions for my security for my configuration for the clusters. I want to provision for the applications that need to go out to it. So all that with just this single infrastructure build out and let's take a look quickly and get here, we'll get it to pop out.

A

I was able to build out a bunch of policies provision. Some clusters apply policy to those clusters. In this case we actually go out and we deploy openshift get offs, which is argo on all of those clusters as well.

B

So it was really really cool um acm. So a lot of people. I get asked a lot working at red hat, um working on the argo cd project about acm, because there are, you know I'll, be the first to admit, there's a lot that are very similar in terms of application. Delivery right.

B

Argo cd is very focused on application delivery, whereas acm, you know we kind of have to step back and think about things that exist outside the cluster things that um you want to automate alongside your git ups practices, and so, um whereas argo cd can manage the continuous deployment continuous delivery aspect of it. Well, what manages the cluster life cycle?

B

I always tell people if you call acm a get ops tool, you're, you're selling, acm really short, because it's it's a really really cool tool um used to deploy and manage your clusters can integrate with argo cd. Also, what you can do is um um from from the get go, deploy application sets with argo cd, so they're the and we're working on putting that integration. It's really really cool.

B

I was so happy to have uh josh packer come on one of the one of the architects engineers for acm, so that was really cool, so um moving right along to other things that integrate with uh get ops and some of the things that you want to talk about when you're working on your get ops um journey here uh in episode, 24, we talked about get ops with acs red hat advanced cluster security. It was all about security, security, security.

C

Earlier in 2017, stackrocks was a more container-focused security service and you'll, hear cloud platforms and container focused platforms that are out there, but we really pivoted to kubernetes, and it's because kubernetes has a specific challenge that it presents to developers and operation teams. That is slightly different from let's say, a serverless process. There are a whole array of configurations with kubernetes that are challenges, and if you want to deploy at the speed at which the developers can introduce functionality into your applications, you need a security process that can keep up with that.

C

So it's about securing the supply chain, securing the infrastructure and making sure that your workloads um that that that process fits in with the developers and the containerization techniques that you have so that you can securely scale to start off. uh We have an openshift cluster set up. This is fairly recent. I think I set this up a week ago and about.

C

Nice uh good reference and um installed some demo applications and installed a couple operators. Acs can be installed as an operator in your cluster, and I think I have four here so we have quay. We have openshift pipelines, we have get ops and we have acs in the cluster.

C

It pretty much is as simple as coming in enabling openshift cluster or advanced cluster security for kubernetes speaking uh picking the specific namespace that you want. um I called it stackrocks because gotta keep the name alive. Somehow that's.

B

Right, you gotta, you gotta! Keep that flag going yeah.

C

Yeah and once you get in here, you'll see that uh part of the differentiation of the the architecture that I showed you is there's a central component, which is the ui and all the tools for analyzing all the information and then there's the secured cluster component.

C

So the central cluster component is the one that you're going to want to install first, it's deployed initialize it'll, give you the ui that you can go into and then you can bring on clusters as you go, and you can do this in an automated way by basically generating the certificates and then, as clusters, come online they'll automatically get populated and they'll reach out to the ui to say: hey, I'm here or you can do it manually, just so that you don't have that automation aspect of something reaching out to your your ui, but you have that capability so with I'll just go right into it.

C

Have a couple applications installed on here. I think I was actually given some pretty insecure ones and I haven't seen them yet so interested to see what pops up now. This is just the main dashboard which I should probably zoom in on again to 200, so everybody can see, and we only have one cluster if you had multiple clusters. Obviously this would show up here you'll see, system violations, compliance standards, it's your clusters at a glance, dashboard.

B

So so, um what's funny is I don't know if you're following the chat is that michael foster actually joined this this stream um on uh he started watching as his his number came up, so yeah michael foster, right as he's tuned in he's come on, so uh he can actually keep me to be honest here. As I kind of summarize here, uh we talked a lot about automation and using get ops.

B

You know um as a working model to um of your your devops practices right, it's a devops working model, uh but you should never forget about security. um Automation um doesn't mean that you need to slow down for security right. Security needs to be part of that process. I know, michael, um if you check out episodes uh that episode. 24 uh michael, went into that whole aspect of supply chain um and also kind of made fun of me for the applications. I gave them how they were being so insecure.

B

um That was it was. It was a fun stream. It was great having them on um and yeah. I check out um acs. It's really good. You need to um build that whole idea of devsecops. You need to build that into the automation and get ups being the cornerstone of automation. You should also think about security as well, so really cool so um remember. Hit uh like like subscribe.

B

Follow us follow me on on twitter um christianh814. If you disagree with anything on this list, let me know I want to hear it. um I want to hear your thoughts as well. So remember, please, like subscribe and share as we go into number five right. Number. Five is actually one of the things I really like our first get ops con. So.

B

So what we did um with get ops con is that I, um if you guys, haven't, haven't don't already know. I am a member of the get ops working group. uh It's a working group um that manages the open, git up sandbox project in the cncf, um and we had our first get ops con at co-located at um kubecon eu uh 2021. So it was a virtual event, all virtual event.

B

It was really exciting. I was part of the programming committee. It was really hectic for those who haven't been part of a programming committee. It's it's it's it's a lot of work right, but it's a labor of love. um It was really cool to get um devops practitioners and people who are curious about get ups, getting all their thoughts, uh their their end user stories. It was really really really cool. um One of the things that I was I was a part of um there was a lot of excitement around it.

B

I had to wake up really really early because it was the eu time zone. It was. It was fantastic, so um really really cool. So on the heels of that on the heels of of uh um get ups. Con number four is I'd like to introduce argo khan. Very first, argo khan.

B

What was really cool is that not only did I what I did, I helped with argo khan. um I also, I also uh did a talk in argo con, so that was really cool. It was really cool to be able to both uh help with the planning and also get my talk accepted. So for those of you who think that, like the kubecon cfp process is rigged or whatever I can tell you it's not because my talk got rejected at get ops con and I was part of the programming committee.

B

So just let you know it's all fair, but I was lucky enough for um to get selected for uh argo con.

B

I talked about uh staple applications, which is funny because my talk for staple applications is something that I've done on the show before, but I didn't put in the top ten interesting, um I'm not sure what that what that tells you up there, but uh yeah argo com was a lot of fun. We had over 3000 people register for the event we held steady at about 500 active members at at a time um lots of lots of great people a lot lots for for a virtual event.

B

It was really really well uh received and I connected to a lot of a lot of really cool people from all over the world, so it was really nice excited for argo. Con 2022, we're still talking about that, um but yeah. That was uh one thing that came out at uh was argo con, so going in to number three is our second get-ops-con.

B

So our second get ops con. I was actually um lucky enough to do a keynote right, so a sponsored keynote, um usually our um um our uh our product manager was um usually does uh the key to the sponsor keynotes. But um I was lucky enough to to do the keynote it was. Actually. It was our first in person get ops get ops con, so um it was in person.

B

um It was really cool here in la so I got to go because it was just you know my backyard. It was really really cool to be able to connect to everyone in person. A lot of the people that I interact with um uh you know virtually. I actually got to see it in person shout out to people like uh like scott rigby uh dan garfield, who are members of the the working group um they were there. We got to meet in person, chris sharp was there, it was it was it was it was.

B

It was a lot of fun. My favorite part of get ops con was actually the end user talks that was really really cool to hear people like from spotify from um um who was a starbucks right, uh state farm, great great, great end user stories there. So all right cool, so uh moving along here um right right along is our number two number two episode: 23 directory structures battles I get opinionated on this one.

B

So the first thing is dry right, just like with coding infrastructure as code get ups. It's all the same thing. We're all talking about code and we're all talking about. Don't repeat yourself right and you know um basically is avoid duplicating your yaml, so um you know like how do I essentially, the question is like well: how do I deploy all this yaml across multiple clusters without copying and pasting yaml everywhere right? So it's it's like uh um it's a trap right, it's the same.

C

A

B

So it's like so again with my example. Right I dumped everything in one one yaml right, it's like well! If I want to deploy this deployment to another cluster, and I just want to change the the scale right instead of replicas one replicas equals two. Do I just copy that directory and just change one line right? It seems like a big waste right.

B

It seems like I'm just repeating the same animal over and over and over again right, so um so income's customized to the rescue right, customized, yeah, he's customized right, so um customize has been around for a while and it's even built into the cli, like you know, ctl or oc since, like 1.14, it's been yeah, it's been there for a little bit, it's been there for a while right and what customize is is a patching framework right. So you um it's it's. Essentially it's like okay!

B

Well, I want to take this yama and I want to patch it right. So um so you can do environment specific changes by using the same um uh same yaml right. So it's not a templating per se right, although you can use it like template um it.

B

Essentially, it produces raw yaml, so the idea is that it just gives you raw yaml um and you can directly apply it so, um and the basic concepts of customize is that you have a series of bases and overlays and the base is essentially what's common amongst all clusters right, so the so. If, if you, if you think about it right, you're, you know what's common across deployment, the differences between the deployments from one environment to another can be it's actually very minimal right. It could be like the secrets.

B

You use the image you use, and maybe the scale but like the rest of it like in in terms of like a skeleton. It's essentially the same right, so you don't. um um You know you don't want to be copying all that just to change a few things right. So this is the concept of an overlay. Essentially, I want to overlay my changes on top of the base configurations.

B

So, um and the thing is, is the base has no knowledge of the overlay? It's just raw yaml yeah, it's just yaml. So the thing about customize is that you, just you just use raw yaml for everything so um and then the overlay is essentially just a series of patches against that. So how that looks like is um here's an example here so again, just to kind of uh wrap it up kind of little bow is the uh get familiar with customize get that power under you, because that's going to dictate a lot.

B

Ask yourself questions like you know, you know what does my environment look like? What does my organization look like uh who's controlling what that will then be on customize, then we'll tell you what what kind of repos are you going to be using.

B

All right so um anytime, I talk about best practices like directory structure always comes out, and I should always really say the best practices for directory structure is really best practices for customized, I'm a big fan of customize um when you first start with get ops and your directory structure and trying to layout you, you first start with a bunch of yaml, and you quickly realize that you need some sort of templating agent right, whether you're you're you're, you're, all in on helm or when um or when you're uh uh you know using raw raw yaml file um you can customize is just gonna, have to kind of have to be there somewhere.

B

So I always say dry right, don't repeat yourself, meaning! You know why. I have the same yammel a hundreds of times if the the change is minuscule right as you'll see as you'll realize in your uh um as as you're copying, yaml everywhere as you're putting yellow everywhere.

B

The yaml doesn't change that much like you, you like to think it does between environment, environment yaml, doesn't change that much. Maybe the image tag and the the the, for example on the deployment, the image tag, and maybe the replicas, um maybe the secret it it really is. You just really should store the delta and I always highly recommend um using ammo right so yemo, um because there's going to be yaml everywhere, and so um you know try to minimize that right. I always do don't repeat yourself anytime.

B

I talk really directory structure best practices is really customized best practices. I should probably I'm going to start saying that right so anytime, someone asks me I'm going to start off by saying that directory structure best practices is, um is basically customized best practices.

B

So that's one of the things actually, the next stream that I do when we come back, I'm actually going to show you how I, um how I lay out my directories structure, so stay tuned right when we come back in january, um cool all right, moving right along so number one all right, I feel like I should have like a drum roll or you know um I should have put like confetti right out when I say this here or uh maybe maybe next year, all right, we'll figure out some sort of drum roll or some um some confetti that'll come out.

B

uh Maybe hire some dancers, something really cool number one. The number one cool thing, the best thing that I think that came out in the get ops world was the get ops principles.

B

So the open, getups right so opengetups is a sandbox project um that is uh managed by or as I guess is, driven by the get ops working group right. So there's a working group and then the actual sandbox project um is open, getups and no longer.

B

So, what's really cool about this about the actual principles which is by far the favorite thing to come out this year is, um is the version one of the principles right so this this is no longer an idea or a buzzword right. So now it actually has get ops now has a charter um and and kind of a guidance right for those who want to dive deeper into get ops. So um this is a huge milestone for us right. I was kind of part of the the principles committee right.

B

A lot of blood, sweat and tears went into this a lot of argument. Oh, when I say argument, I mean our argument in in the uh in the adult sense right now in the child sense, like kind of like um kind of discussions right, he did uh discussions um opinionated discussions coming out of that uh great huge milestone um if I'll actually drop it in the chat.

B

If you want to read up more about it, um go ahead and go to opengetoffs.dev right, there's a I put a link to the blog announcement there um going really quick through these. um These principles. Right is that uh first principle is that it's declarative, but read it straight out. The way it is declarative, a system managed by getups must have its desired state expressed declaratively, so um kind of self uh um self-explanatory. This is infrastructure as code. As you see it today, right stored in git.

B

This is kind of what number one is selling you doesn't call out git specifically, but that's kind of what it means.

B

uh The number two thing the number two uh principle is: it's version and immutable right and so um desired state is stored in a way that enforces immutability versioning and retains a complete version of the history right. So this is kind of where git shines or any source control management system shines. Where is that you want that mutability right immutability?

B

um You want that that version of the desired state immutable um it's pulled automatically.

B

So when there's a change that change is, is pulled on to the system right, so there's a software agent that automatically pulls the desired state declarations from source right, whether that source is git or whether it's s3 bucket whatever it is right as long as it satisfies uh the number one and number two right, and the fourth principle is that it's continuously reconciled. So this is where it differs right. So a lot of people say: hey I've been doing get ups forever. I do um you know anytime. I make a commit.

B

It triggers a um a ci process that does everything that get ops does like. Well, no, no, no, not exactly right so continuous reconciled. This is the nuance right, whereas where it differentiates it from traditional event-based, ci cd process, software agents continuously observe the actual system state and attempt to apply the desired state. So this is um the idea of a a closed control loop right. So if you, if you guys, um look up a control theory, let me actually um see if I can pull that up. Really quick right.

B

There's a um this control theory um I'll I'll. Look for it, maybe maybe a little later, um because there's a lot of stuff that comes out she, but um the uh control theory right is that um there's a feedback, loop and there's a loop that happens so then it basically checks for the desired. You know the the input is a desired state and it checks continuously.

B

If that desired state is satisfied- and you know it'll reconcile that right. It kind of sounds like kubernetes think about kubernetes right deployment.

B

If the deployment says there's two replicas, but there's only one replica it'll spin up another one sort of thing right so kind of same idea, but taking that to an application saying that as holistic so really really love um what we did right right with control theory, uh putting that control theory there um I actually wrote a blog that kind of called this out a little bit. um It's uh the new stack blog. I think um oh uh um shari he's he's on.

B

If you could post that put that in the um in the chat, um well lead yeah, it'll, it'll help um and so um yeah. So actually a good comment right three can be argued, pull versus push. I think that um um that's something maybe in version two right, I think either one works, pull and push as long as that reconciliation, loop happens.

B

um So that's kind of the uh the the the idea. There is control theory and I always like to spend a lot of times there with number one, because one it's number one and and it's one of my favorite things and also it actually gives git ups, an actual thing right. An actual model to follow lots of great things, remember to get involved, open, opengetops.dev.

B

um You know where it's an open community. Anyone can join. You know, there's no formal process. You just join a meeting volunteer for stuff again things that are coming up. I'm part of the program committee for get ops con eu 2022 right in valencia, we're going to have it in person, so we're going to do something, also something cool there. uh We're planning, hopefully we're planning on having dual tracks, we'll see.

B

Still a little early, um you can register for it, though now so, if you reg, if you're registering for kubecon, you can also add on gitobscon, um you know it's it's it's right there uh when you register, so um it's hope to see all you guys there. Thank you! uh um Well, he he put that the new new stack article I have. I talk about argo and flux, but I also kind of briefly mentioned control theory there, um where you can read up more about it.

B

So um with that, I think that I think that's it. um um I just kind of want to thank everyone right. Thank thank everyone who again. First of all, thank you. Everyone for up um kind of working with us in the technical difficulties. In the beginning, I like to blame aws because it's just they're an easy target, but who knows what the issues were, um I'm just kind of picking on them because they had those outages this week. um So thank you.

B

First of all, for those who have put up with that um uh and um second um we're gonna be taking again, like I said in the beginning, uh a little break um we'll come back on.

B

Actually, let me pull up my um uh calendar because I'm not sure when we're coming back, I think we're coming back on the 13th and yes, we are so we're coming back uh january, 13th we're going to start an hour later, um there's going to be an episode of a special episode of in the clouds right, so I won't um ruin that for you, um but we're gonna start an hour later. um Instead of noon, uh pacific time, we'll start at uh 1 pm pacific time, which is 4 p.m, east coast time.

B

So you know I'll I'll remind you everyone um when that episode before that episode comes out, that um you know that just for this one episode we're doing a little hour later so um yeah. So um with that, uh I would say: oh yeah, one thing one last thing: um um we have a survey, um I'm keeping this up here.

B

Until oops, no, I can never get this.

B

I did have a bitly here, um maybe.

B

B

Just a day of technical difficulties, there we go so survey um survey, I'm gonna keep this up till the end of the year right. So, if you haven't filled out the survey go ahead, fill that out we'd like to hear from you how we can improve the show and actually one last thing. I keep saying one last thing over and over again, but uh here we go one last thing right, so we are.

B

um We are looking um for a co-host right and so, um as you know, chris left- um and uh we are- uh you know diligently looking for a co-host. I do we do plan on having a co-host.

B

So if you're, a red hatter reach out and uh um and we'll see, um you know if you're interested we've already talked to a bunch of people, I think I've narrowed it down to it to a few people, but um things to look for in 2022 uh a co-host. Hopefully we'll get a permanent co-host here. So it's just not me rambling.

B

I can ramble. I don't have problem rambling, but maybe you guys, um you know it could be helpful to um uh get another perspective as well. So it's just not me pontificating. So with that I'd like to close out 2021 um 2021 um again crazy year, hopefully it gets better 2022.. uh I I'm excited for what the show brings in 2022. So again, like I say: if it's not um it's not in git, it's only a rumor so take care of yourselves out there. Bye, bye everyone.

B