The Grape Nuts and Grape Nuts Flakes program starring Jack Benny with Mary Livingston, Phil Harris, Dennis Day, Rochester, and yours truly, Don Wilson. Speaking of New Year's resolutions, here's a poem for your friends. So listen. When the year is at the morn, resolutions fine are born. When the year is old and gray, resolutions, where are they? I have the answer here to a season full of cheer. Just resolve to start each day happy, carefree, blithe, and gay. And you know, folks, all it takes to start the day is Grape Nuts Flakes. That's the answer, all right. Eat a good breakfast, do a better job. Because you need an adequate breakfast after a fast of 10 or 12 hours the night before. In fact, dietitian tells us that morning is the time we should get at least one quarter of our entire day's nourishment. Yes, breakfast is the stoke-up meal. And Grape Nuts Flakes are certainly a swell tasting stoke-up food.  So for 1944, let's all resolve to eat a good breakfast, do a better job. And let Chris Toasty Brown Grape Nuts Flakes help make it easy for you. Since this is the start of a new year, we bring you a man who at the age of 20 began his phenomenal career in show business. That's right. At 30, he was a credit to his profession. Yes, sir. At 40, he was admired and respected by millions. That's me. At 50, his name became a household word. 50. At 60, he became... All right. Stop. That's enough already. For heaven's sake. And here he is, Jack Benny. Thank you. Hello again. This is Jack Benny talking. And Don, it's a good thing I stopped you or I'd have died of old age before the show started. 40, 50, 60. I wasn't so very long ago that I was going to Warkegan Grammar School. I know, Jack, but you were the only kid in class the teacher called Mr. Don. They didn't call me that till I was in the sixth grade. And anyway, Don, it does... Hello, Jack. Hello, Mary. Anyway, Don, it doesn't... Fine thing. I hurry over here and nobody even notices my new dress.   Oh, that. Well, Dennis gave it to me for Christmas and I'm wearing it so I won't hurt his feelings. You mean Dennis gave you a... Oh, wait a minute. He must have gotten the boxes mixed up. What do you mean? Well, Dennis gave me the cutest pair of lace panties all covered with rose buds. Oh, gee, I'd love to have those. Jack, I'll give you the necktie and you give me the lace panties. Well... Oh, Dennis really meant them for me. I know, but... You didn't lose them, did you? I hope not. Oh, so that's it. You didn't want to hurt his feelings either. Look, Mary, when someone gives you a gift... I know, I know, but Jack, those panties were supposed to fit me. How in the world did you get them on? Oh, I didn't have much trouble. You didn't, eh? I'll bet those rose buds are stretched a full bloom. Never mind. Let's see, where was I? Oh, yes. Now, look, Don, the next time you make a remark about my age, you better first... Hello, Mr. Benny. Oh, hello, Dennis. Don, the next time you make a remark about my age... What's the matter? Oh, Don's always telling people that I'm a lot older than I am, and I'm sick of it.  Dennis, they gave me this cane with my sports suit instead of an extra pair of panties.  Anyway, to change the subject, I'm glad you're all here early tonight because we have a very important program to do. What do you mean, Jackson? You'll know in a minute, ladies and gentlemen, as is our custom at this time of year, and even though it is January 2, tonight we are going to present our annual New Year's Play entitled The New Tenant, or Goodbye, 43, Hello, 44. I hope you will all enjoy our latest version. Now, once again, I will play the part of the old... Hey, Mr. Benny, every year you do one of these plays, and I don't understand them. Well, you see, Dennis, these little sketches we do at the close of each year are not so much plays as they are allegorical fantasies.  No. Well, Dennis, an allegorical fantasy is like a... Well, look, kid, did you see Snow White and the Seven Dwarfs? Oh, yeah, yeah, sure. Well... I didn't understand that either. Dennis, it's all very simple. Look, my play and Snow White are in the same category, in that they both deal with the abstract and the esoteric rather than with the prosaic. Prosaic? Yes, that's it. What is it? Don't worry, Dennis. Jack doesn't understand it either. I understand every word I said. Sure you do, Jackson. How do you know, Phil? Because I'm the guy who learned it to him. Phil, if you really want to help me keep quiet, keep quiet. Look, Dennis, Dennis, an allegorical fantasy is a... Jack, what do you want to show off with big words for? Show off? If you want to explain something, do it simply and direct. Don, don't tell me how to... When I want to tell somebody about grape nuts and grape nut flakes, I don't go in for verbal calisthenics. No, Don. All I say is that grape nuts and grape nut flakes are two delicious cereals that always taste like more. But look, kid... Grape nuts, crisp and crunchy, grape nut flakes, tempting toasty brown flakes. Don... Both have a zesty, moldy-rich flavor that's distinctly their own. I know it's their own. They're made of sun-ripened wheat and malted barley, and they bring you energy-giving body-building whole-grain nourishment.  Oh, it zips, it zips. Simple enough. And so eat a good breakfast, do a better job. Feature grape nuts or grape nuts flakes.  You're absolutely right, Don. Come here, kid. I'm going to explain it to you in simple words like Don did. Oh, you don't have to explain it to me. I thought about it while Mr. Wilson was talking, and I know exactly what you mean. Good. Now, what is an allegorical fantasy? A prosaic bowl of grape nuts flakes. Well, look, Dennis, I'll explain it to you later. Meanwhile, in our fantasy, you're going to play a double role. The parts of the two most despicable men in the world, Hitler and Tojo.  Yes. Where's a mirror? Why? I'm going to spit right in my faces. You don't have to, kid. You're only playing the parts. Anyway, you're going to be Hitler and Tojo tonight. Well, okay. But I'll just hate myself in the morning.  Uncle Sam? Yes. You see, in our sketch, I will play the part of the old year, 1943, who has been living in a big rooming house called the United States, run by Uncle Sam and his wife, Columbia. Now, Mary, you're going to be Columbia. You have 48 children, one for each state in the union. I've got 48 children? Holy smoke. Mary, it's only an allegorical fantasy. Well, this is a fine time to tell me. Mary, I tried to explain it to you. Your children are the 48 states. Each state is a child. Oh, then I better hurry and change California. It's wet again. Don't worry about it now. Anyway, ladies and gentlemen, we set the stage for our play, which will go on immediately after a song. I'll get it. Hello?  I've been down to the stores exchanging your Christmas presents for you. Oh, yes, yes. You didn't have any trouble, did you? Only at one place. They refused to give you a refund on your Christmas tree. Well, it was worth a try, anyway. And say, boss, while I was out for you, I tried to exchange a present my uncle gave me. Uh-huh. But the store wouldn't do it just because I tried it out for size. Well, that was mean of them. What was the gift? A bottle of gin. Well, no wonder they wouldn't exchange it. And Rochester, why don't you try to reform? Oh, I did, boss. Remember yesterday I made a New Year's resolution not to shoot craps anymore. Yes, I remember that resolution. What happened to it? Rochester, have you been shooting dice again? It wasn't my fault, boss. Some of my friends came to visit me. Yes. It was the first time a group ever came through a door on their knees. Oh, so you got right in the game, huh? No, I didn't, boss. I tossed a coin. Heds I shoot craps with them and tails I don't. Uh-huh. And I suppose it landed head. No, boss, it landed tails. Well... As I bent down to pick up the coin, two small cubes fell out of my suit. Uh-huh. And to my, I'm throwing a seven. That later. Where are you now, Rochester? In a phone booth on Central Avenue and I...  This is a high phone. Rochester, have you got a girl in the telephone booth with you? It ain't an allegory for fantasy. Rochester, I'm surprised. Oh, my, boss. She ain't the same one I came in here with. I haven't got time to talk to you anymore now, so I'll see you when I get home. Goodbye. Goodbye. Oh, say, boss. Now what? There was a phone call from the freight company telling me to come over because your camel had arrived from Egypt. My camel? That's wonderful. Well, listen, Rochester, don't tell anybody, and I'll spring it on my friends as a surprise. Well, you better wait till the wind is with you or the element of surprise will be lost. Well, don't worry. I'll take care of it. See you later. Goodbye. Goodbye. I'm glad the camel finally got her up and waiting long enough. Sing, Dennis. Or goodbye, 43. Hello, 44. As the curtain rises, it's almost midnight of December 31st. An old man, 1943, is packing his bags and ready to make his exit. Curtain. Music. You want 43? Give me a hand with this packing, will you? I've got to get out of here before midnight and make room for the new tenant. Oh, yes. Little 44, I'll be here any minute. Say, where's your husband, Uncle Sam? I'd like to say goodbye to him. Oh, he's around someplace. Sam's been pretty busy lately. You said it. All your kids have been pitching in, too. Here comes one of my relatives, the Navy. Oh, yes. Hello, Navy. Hello, old timer. Hi, Columbia. Boy, has he grown. Yep, his tonnage is almost doubled. He's big all right. Nice to see him so healthy. By the way, Navy, how's your wife? Oh, fine. Fine. And congratulations are in order. Really? Yep. Triplets. Three new battleships. Well, congratulations, Pappy. Here's a picture of them. Well, I'll be doggone. They got their mother's nose and their father's keel. Yes, sir. Well, so long. See you later, Columbia. Hey, he needs a big family. He's got two bathtubs to fill. Guess I might as well finish packing. Columbia, hand me that bundle of swing music. I'll take that with me. Here you are. Thanks. Lay that pistol down, babe. Lay that pistol down. Boy, am I sick of that. Say, Columbia, I got a few minutes yet, so I thought, well, hello, Eleanor. Glad to see you back. There she goes again. Say, Columbia, I started to tell you, I've only got a few minutes, and I thought that maybe before we... Oh, hello, Sam. Well, Uncle Sam, where you been? Oh, what a week. What a week. I've really been busy, been sending Christmas presents to my nephews all over the world.  And say, what's that button you're wearing on your lapel? I never knew you took sides in politics. Well, I don't. I don't care if it's the Democrats or the Republicans. They're both good. But that button... Well, come closer and take a look at it. Okay. Well, I'll be... Well, what does it say, old timer? Frank Sinatra. Well, Sam, it's good to know that with all that's on your mind, you still find time for a little entertainment. That's right, and that ain't all. Look down here. Bobby socks. Sam, you'll never grow old. Hey, Columbia, turn on the radio. I want to hear the World Series. This'll be my last chance to hear the big game. Okay. Ladies and gentlemen, you are now listening to the final game of the World Series between the United Nations All-Stars and the Axis Pullcats. That's it. That's what I want. Me too. A lot of my boys is playing in that game. But the benefit of you people who tuned in late, this is the last half of the eighth. The Axis had their inning and the United Nations are now coming up to bat. Because of the game, the Axis did pretty well. They pulled a couple of sneak plays and tried to steal a few bases, but they were stopped by a squeeze play between Timerschenko and Montgomery. Those boys are sure a couple of big leaders, all right? You said it, old timer. And now, folks, before we resume our play-by-play description, I would like to remind you that this broadcast comes to you through the courtesy of Freedom Unlimited. That's a great product. All right, folks. The United Nations are now at bat. The coaches are George Marshall at third, lifting up to the plate. Heaviest hitters we got. Yep. He's got a darn good batten average, too. As you know, ladies and gentlemen, the battery for the Axis is Tojo pitching and Hitler catching. An old boy is he catching. You're not kidding. And here comes the first pitch. It's... So he got a man on first. Yes, sir, he... Incidentally, folks, in the sixth inning, Mussolini got hit on the head with a ball. So now the Axis will have to get another water boy. Well, he never was much anyway. All right, folks. MacArthur is on first base and coming up to bat is Chiang Kai-shek. On everything he does is low. Yeah, he's been thrown some nasty curves, but our boys are getting wise to him. Chiang Kai-shek is standing, grimly determined at the plate. Here comes the second ball. This is MacArthur's sacrifice. I knew Chiang Kai-shek a sacrifice. That's the kind of a fella he is. Yep, that's what I call great teamwork. While we're waiting for the next batter to come up, let's have a word from our sponsor, Freedom Unlimited. Ladies and gentlemen, do you spend restless nights because of a haunting fear that you may lose your rights? You're right to free speech. You're right to worship as you please. And you're right to live without fear of aggression. If you do, ladies and gentlemen, get yourself some shares of Freedom Unlimited. And you can do that by buying war bonds. Remember, folks, Freedom. Spelled F-R-E-E-D-O-M. Aunt Felisure knows what he's talking about. And now back to the game between the United Nations All-Stars and the Axis Polecats. Well, folks, the crowd is sure excited. MacArthur's on second base and coming up to bat is Montgomery. Sure is a fine player. That's right, Sam. The pitcher's winding up and here comes the ball. He tries to stop it and MacArthur goes to play. Don't claim them. Hey, Sam, that Rommel ain't doing so good, is he? No, he ain't. He's the best player they got. That's right. And now, folks, uh-oh, what's this? Hitler walks out to the pitcher's mound to talk to Tojo. It seems they got their signals crossed and Hitler's worried. But there's a switch in the battery for the Axis. Hitler is now going to pitch. A lot of good that'll do. Hitler used to have a pretty good arm. He already exercised enough hanging wallpaper. Yes, ladies and gentlemen, Hitler is in the pitcher's box and coming up to bat for the United Nations is Tim O'Shinko. He'll knock Hitler out of the box and then put him in one. Wait and see. And here comes the first pitch. Ball one. Very wide. See that, Sam? Hitler's nervous. He's winding up again and here comes the second pitch. Ball two. You know, something old-timer, I think Hitler's afraid to pitch to him. Here comes the third pitch. You're right, Sam. Yep, Hitler doesn't dare take a chance with Tim O'Shinko. O'Shinko walks to first, putting three men on base. Tim O'Shinko on first. Montgomery on second. And MacArthur on... One good hit now. Put the game in the bag. What a bold game. What excitement! Bases are loaded for the United Nations and the Axis team is plenty worried. This is the tensest moment of the game and the question is, oh, there's a conference being held in the United Nations dugout. Co-managers Roosevelt, Churchill and Stalin are putting their heads together to decide on the final move and... and... Wait a minute, folks. Wait a minute. They've reached the decision. They're sending Eisenhower to see what's going to happen. I'm afraid you won't be able to 1943.  But I want to hear the end of the game. Well, I know how you feel, old-timer, but you just haven't got the time. Okay, okay, turn off the radio. Anyway, I got a pretty good idea how it's going to turn out. Dog gone, look at that clock. Just got my duds together in time. Hmm, that's the first stroke of 12. I wonder what's keeping the new tenant. Little fella should be here by now. Well, don't worry, he'll show up. He always has. Say, here's a tip for you, Sam. You worked hard during the time I was here. You did a good job. And I want you to work even harder for the little fella that's coming in. Don't you worry, old-timer. I'm really rolling now. Hmm, time's a fleeting, but I can't leave till that little shaver gets here. That must be him now. Yep. Come in. Well, it's the little new year. Hello, Sonny. Hello, old-timer. What's that you got under your arm? Some forms I'm going to try awfully hard to get signs this year. Yeah? What are they? Well, here's the most important one. It says, un... un... How do you pronounce these big words? Let's see that. Oh, that says, unconditional surrender. Well, I hope you get them signed during soon.  Glad to know you folks. Hello, Sonny. Hiya, bub. You ought to have a coat on with them diapers. It's pretty chilly tonight. I was sure cold the first night I got here.  With all the pop bottles and peanut shells laying around, you're going to have to clean up the field and put it in order again. I'll do the best I can, sir. I know you will. But tell me, old-timer, how's the game going? Well, at the start, things didn't look so good. But after a while, hear that, Son? Yes, sir. What is it? That's being played for some of Sam's nephews. They were good ball players and hard hitters, too, but they were put out early in the game. Wasn't their fault? Pitching was a little too fast for them then, and it wasn't fair, either. The man that had my job last year told me that Tojo started pitching before the umpire said, play ball. That ain't baseball, Son. Not like they play it in America. Well, I've got to be mowsying along now. Oh, by the way, Son, Uncle Sam's got a nephew called Franklin that's been taking mighty good care of him. Ain't he, Sam? They're dirt tooth. So keep an eye on them, Son. Give them all the help you can. Franklin, eh? I'll write that down. And here's some more names for you. There's Winston, Joe, Chung. A whole lot more to Sam will give you. I ain't got time to mention them all right now. I'll make a note of them. Leave it to me. Hmm. One more thing, Son. When I came in, there was a name given to me and I was instructed to pass it on to you. And I want you to pass it on to the next little fella that takes over. Who is it, sir? The name is Colin Kelly. He represents all our boys who only got one turn at bat. Remember that, Son? I will. Well, gotta be leaving now. Goodbye, Sam. So long, old timer. Well, here I go. So long, 43. So long, Columbia. Keepin' flyin'. Back many program, the makers of Grape Nuts and Grape Nuts Flakes send you their very best wishes for 1944. Good night, everyone. Thank you.


Welcome to All Hands Update. I'm Petty Officer Ian Cotter. These are your headlines from around the fleet. February is National African American History Month and this year's theme is a century of black life, history and culture. African Americans have served with honor and valor in the defense of our nation since the 18th century. This month we will remember the many brave actions of African Americans, actions that shaped our country and our military. Visit Naval History and Heritage Command's website for more information. From flying F-A-18 Hornets off the flight deck to flying a spaceship into outer space, one Navy captain has seen it all. Captain Barry Wilmore, commander of NASA's Expedition 42, currently on the International Space Station, made a very long distance call to the crew of USS Theodore Roosevelt. He answered questions from the crew and shared his experiences as a naval officer in space. To find out more about their experience, visit the ship's Facebook page.


Welcome everybody, thank you for joining us. You are the Friday crowd. You're the Friday crowd.  Great job, yes. Time to play fights. Yeah, so we're gonna talk about how Adobe planned for scale with Argo CD, Cluster API, and Decluster. Joseph, you wanna introduce yourself? Yeah, I'm Joseph Sanibel. I am with Adobe, which is just in the title. I am now a product manager in our Dev Experience group, which really means that I'm still working with the underlying Kubernetes infrastructure, and then in this alternate life, I get to hang out with Kubernetes SIG release team, and part of like five release cycles, branch release manager associate, still trying to retain it because that's one of the things I highly value. Yeah, and I am Dan Garfield. I am the co-founder and chief open source officer of CodeFresh, and I also feel like I live a dual life because I'm also an Argo maintainer, and then I helped start the GitOps working group and open GitOps as the GitOps standards that are a CNCF project that I've been very pleased to see a lot of pickup on a KubeCon and lots of people's lines. So we're gonna talk about Adobe and how you're scaling. Yeah, so a lot of us are familiar with the brand, but that's just like one aspect of what we do at Adobe. We have an analytics area. We are very big in AI and ML and improving our products with these types of developments. And there's also other areas like marketing, and so there's quite a bit of a portfolio that Adobe has. And so if you've hit up any of the talks this week, you probably, there's a couple of people here who have been speaking about what's been happening there, but you may have heard the name Ethos, but what Ethos is, it's the cloud native platform. If you're gonna do anything there, that's the spot it's gonna happen at. And this platform has existed for about five years. And so a lot of change has happened, a lot of developments. The interesting things about it is that we've scaled. And so the cluster counts have grown. It's dynamic. We have about 230 clusters, roughly 18,000 compute nodes, 1.8 petabyte of memory and about 500,000 CPUs. Along with that, the project is growing. I think the last count was 2.3 million. And along with it, we were a company of about 26,000 and you can imagine a lot are developers. So the great thing is we're scaling, change is happening there, and it's exciting to kind of see. And we're pushing things as far as it goes. But with that though, that also presents some challenges for us because a lot of us know who are running platforms. And when I refer to the platform because we have quite a few teams who are doing a lot of different things there, the team I'm on is really foundational. And we really care about like providing that bedrock that the teams that are building like the developer experience or the paid path or the teams that are like these large scale, dedicated clusters that they have the space to be able to do the things they need to do. So we get a lot of requests. And some of them are, hey, we've got an environment that we wanna be able to test our changes. We want femoral clusters. We want these things to spin up on demand. And a lot of us from our side of it are just like, that's challenging. How do we kind of do these? Because we have some pressures. We wanna keep on on the cost. Some of the other things that I'm starting to see emerge is requests to really push out more clusters. Push compute out further to the edge. Find ways to support a lot of the use cases that are gonna take our products even further. As well as like just getting out of the way. Like really just enabling teams to, some teams wanna go fast. They wanna be able to like be on current release versions. Other teams wanna be more guarded. And we're managing this all the while while we have dynamic times of years where things have to scale while we have holiday periods. And so we really have to create this layer. And this is where the challenge comes in when I have the team that I'm working with is that how do we create that separation or that sensible layer because we have challenges as well. We're trying to keep the fleet current. Trying to keep that fleet consistent. We have components and all these things that make up that underlying platform that really provides it. It's not just Kubernetes. We have tooling that's around security, cost efficiency. As your scale, we have to keep an eye on cost. It is, it is. All right, I think I hear one. Here we go. I hear something. There we go. I think I got it. No, no, no. Maybe not. Let's bring it up.  And with that, there's been a lot of change. And so this kind of lays some of the context of our current challenges. They are made of extra repository. It was very reflective of it. I think we're good. All right. These patients with this, as I was saying, we've been around for five years. And it was very reflective of that start, as I was mentioning. They started off with Mesosphere, which then evolved into Kubernetes. And so a lot of the way that they built and deployed on Mesosphere influenced what happened afterwards, meaning they had a very tightly coupled get repo that it mirrored the structure and the org at that time and how it worked was it was barely tightly coupled. That was great. It scaled us up. We were able to keep a cadence of weekly releases. But then as growth started to happen, things got a little bit slower. There's obviously some challenges because not everybody's on the same release schedule or cadence. But over time, when we pivoted to Kubernetes, well, scale was a little bit different than Mesosphere and how you design things. But the team was able to kind of keep the train going and things were working. But over a few more years, this is when things started to get a little bit more impedance. And this is where we had to start really thinking about where we were headed. And that's because of that tightly coupled nature of how we were building and deploying releases that all changes needed to be reviewed by an all-knowing maintainer. Even though you may have this service that's way over here that you know it very well, but because it touched the core, we needed these individuals to be able to make sure that it was not gonna cause any implosion or any friction or cause a release to have a problem. So that system had really served its purpose, but now it's time to evolve. So we had this idea and I think we were really kind of looking at that time and it was still early in and I think a few of us were looking at the Argo community and we saw some areas where like, hey, there's some challenges there but it looks interesting. But we thought, maybe we could iterate on what we had at that time. Maybe that's the fast way to kind of like unblock ourselves in a sense kind of like decouple releases. And that was our next attempt and I think, Dan, this is kind of about the time I met you. I think we were talking about this where we overlaid Argo workflows and really to do that, we really had to create a workflow of workflows which then made things maybe a little bit more complex, not as like easy, but it did unblock the trains of releases to individual clusters. So that's a good thing. But the challenge of maintainership was still there. A lot of the features that we had to start thinking about was kind of like, well, wait a minute, are we kind of re-implementing something that's out there, which is Argo CD? But we went with it. It was kind of a lift and shift approach. This is kind of what we ended up with, really taking Argo workflows with the traditional CI city approach. I think, Dan, I went to you. I don't know if you made a face or not, but I did say, hey, Dan, what do you think of this idea? Mainly I was just like, hey, scale. How far can we scale? Because I'm looking at the existing fleet that we had running and I'm looking at where we're going to market and where we need to be. And I was like, I see the same down the line, we're gonna hit that same wall. I know you had some thoughts on the traditional approach. You know, we're very used to, and is my mic out? No, you're good. My mic, okay. So we're very used to using CI CD as DevOps teams. We've been using it a long time. We build a pipeline. Like, how many of us have built those pipelines literally 10,000 times?  Maybe I built some logic to do a rollback if I'm getting fancy. And for the use case that you needed to support, which you clarified so many diverse use cases, you needed a really complex workflow to support that. So you had a workflow of workflows so it was intelligently designed, but that also meant that at the end of the day it was very complex. And we all know that in CI CD, it's very, I mean it's an imperative operation. And so creating idempotency inside of a CI CD pipeline is really difficult. I said deployed, did it work? Do I need to add a retry step? And you get into doing retries and these kinds of things and it's not event driven and it's just because implementing idempotency is really hard. So this approach that you had built, it got you from point A to point B, but you were also looking at point X down the line and thinking, how are we gonna scale this? And then we've got Mike Chudron on the team who can manage this, but we don't have 15 or 100 of him. So how's that gonna scale up? And so this is when we started talking about GitOps and I tried so hard not to make a face because I was like, this is cool, this is great. Maybe some things to think about. So this is the approach was, well, we're doing CI CD, let's just extend it, right? We talked about some of the issues with that and how you kind of realize that you're implementing a lot of the features that are actually built into Argo CD. There's a lot of logic in the Argo CD reconciliation flow and those controllers and how they operate to create idempotency, right? To create and simplify the operation. So having to rebuild all that logic yourself, it just didn't make any sense. And it also, because of the way that workflow, workflows and CI CD work, it's fairly rigid and it's more difficult to create these self-service operations. So this is the point when we decided, okay, let's get into a GitOps model, let's get into Argo CD. Now, I think most people at this point are familiar with OpenGitOps, OpenGitOps.dev, the GitOps principles. Nobody is familiar, it's like a handful of people. Okay, so there's a couple, all right. So this is, go to OpenGitOps.dev to pull these up. Go ahead and do it on your phone. There are four principles that go into GitOps. And this involves how we manage state, our actual state and our desired state. And I'm not gonna go through all those principles right now but you should read them and potentially memorize them because basically what we're trying to do is keep track of our actual state and make sure that there's no drift. Drift is when something changes in our state that was not defined in our source of truth. It was not defined in Git. And I talked to a lot of people who, you're like, hey man, I've been using Terraform for five years, I check it into Git, I apply my plan, I feel like I'm doing GitOps. Smells like it. Smells kinda like GitOps. And you're at least halfway there. I actually talked with somebody recently who told me that they went to actually check all their Terraform and they found that over half of their Terraform plans that were old had drifted. And they actually couldn't easily reconcile. So that means that things were getting changed in production that they weren't aware of. And that's shockingly common. So the GitOps style is that you have a source of truth. That source of truth is Git. In the years of past when we're doing CI CD pipelines, a lot of times our source of truth is sort of inferred by the operation that's happening in a pipeline. But what happens when a step fails? What happens when a web hook fails? What happens when the state has changed and you can't detect it? So you're trying to push changes onto something that's not what you expect. All of these situations are the reason that GitOps was created in the first place. So in your case, one of the things that we wanted to do was handle pull request generation. That's right, yep. And that's because with GitOps, the source of truth is Git. So generating pull requests is important. And then generating things off of pull requests is important. Makes item potency easier. And then you also needed to handle isolation because you needed to be able to test operators. Yes, we can't give everybody full permissions on that cluster. So I think that was a big request. Hey, I have a CRD, I want to test these things, but we want to give it to them in a safe manner. Yeah, when you have an operator and you go to upgrade it, it's tricky to test, right? And in your case, you're supporting not only multiple clouds, but multiple Kubernetes versions. So having that all operate together in a GitOps fashion would be very valuable. It is, yep. So a couple of key tools for this. Yeah, so I think the, is in the talk. Of course, I named off all the names that I love here, but I'll start with vcluster. I think this one came on my radar like last year at LA, KubeCon. Lucas gave this great talk and I was just like, wow, this is kind of neat because all of a sudden now we can spin up a virtual cluster that runs in an A space. As far as our developers, they feel like they have full API access. They can do whatever they need to do. But yet we can make sure that the host security is not, is enforced. It's really easy for rapid provisioning.  I want to test this thing. And we want to be able to just let people kind of test as often as they want without breaking each other. Yeah, now those vclusters, in this case, we're going to be defining them using cluster API. If you're not familiar with cluster API, cluster API is an operator that allows us to take manifest describing vcluster or other cluster resources. And cluster API will make sure that those are spun up and reconciled. So because all of these things are essentially just Kubernetes manifest, they're just Kubernetes resources, there is a tool that is designed perfectly well for synchronizing those. And it's called Argo CD. Hands, who's familiar with Argo CD? Okay, most people. So the GitOps thing, people were like, I don't know what that is. But Argo CD, everybody's got it. So within the Argos project, there are four main tools. There's Argo CD, which all of you are familiar with, which is great at reconciling resources, you define a Git source of truth, you define a destination, and the reconciliation engine takes care of the rest. There's Argo workflows, which is a general purpose workflow engine for Kubernetes, and allows you to run any kind of workflow every step operates in its own pod. It's very popular with data pipelines and ETLs, but it's also incredibly popular for doing workflows, scripted events that need to happen. And then there's Argo events, which is for eventing and triggering these things. And there's Argo rollouts for doing progressive delivery. Yeah, so all of these things are great. I would say one note about cluster API as well. We're in this great time where a lot of us didn't have a lot of that API for infrastructure. I think it was always been a cloud-native experience for developers, but as operators, we always kind of like seeing the trail behind and having that and then seeing the maintain of our adoption over the last year was the confidence buildup for me. Anytime I see these projects like reach that inflection point, it's a great time to jump on board. Oops, go back. So this was kind of where we landed at. This is the architecture that, right slide? Yeah, you're good. Okay. This is the architecture that we landed at. It was the one that in this use case and we wanted to target that pull request environment was the kind of like use case where a developer opens a PR and he wants to test the operator or application that we need to give full access. And this application is where the magic of kind of building something is where the application said it's there to the left, upper left is where the magic kind of happens at. And so we use this PR generator to generate like a B cluster in next example with the support of cluster API. And the workflow is pretty basic. It's really just the event source is looking for this new cluster API resource. The Argo sensor picks up the event and sure goes a new Argo workflow. And then Argo works for the new cluster or B cluster to be fully created and gets the config and all the other things that need to be in that cluster into Argo CD. I think I may be in the wrong spot, I think. Yeah. So Argo CD from there really syncs generates all the resources to it. You know, whether it's a Prometheus operator and English controller, you know, all the things that make it that unique property. And then all of a sudden your bootstrap you got this new B cluster. So for us that was like the really inflection point and the great thing about this approach is that it could also be leveraged into regular clusters as well, which we also wanted to do. So this was kind of like that stepping stone. I don't know, V8 Dan, you probably run something similar. Yeah, this approach is just so impressive and strong because it means that you can test those operators against multiple Kubernetes versions and you can do them in self-contained pull request environments that are generated via application sets. A lot of people are familiar with application sets as a way to generate applications in Argo CD, but within application sets we have this concept of generators. And generators include things like a pull request. So all your pull requests can generate applications. All of your Git repos can generate applications. A folder structure, a list, any of these kinds of things and they can be used in combination with one another in what's called a matrix generator. So this environment also allows you to save a lot of money because running a V cluster is ultimately incredibly cheap compared to running an entire cluster. There's a great preview, a prequel to this talk, if you will. There is, there is. Yeah, it was done the other day by Mike Tujron, who's in the audience. If you really want to get into a deeper dive, it's not posted yet. I expect those talks to come up here in the next few weeks, but it's hundreds of clusters sitting in a tree with Argo CD. It's really kind of like a lot more in detail. You can kind of find the patterns that you may be able to leverage yourself. I think it also has a repo that you can pull from as well to see how all this magic happened. But this talk, yes, it is about some of the things that are in my title, but the key thing that I always have my eye on is scale. I have an existing fleet. I know with how big this fleet is gonna be and where it's going in one to three years and I'm trying to figure out, all right, we built this thing, we've had scale things in the past. This is where I'm gonna set you up to hit it out of the park. I came again and this is a true, this is seriously, I was kind of like, what are the scale points? Like, does anybody have any baselines out there that I can pull from? Because I was just looking out there, trying to figure out like, how do I communicate to the team our plan of scaling? And so I think that's when you just, you were like, hey, let me, let me look at this, how can we scale this? Yeah, who's read the official benchmark report from Argo that tells you when you need to consider scale components? Nobody? Oh, because it doesn't exist, right? So that was a call to action because hopefully I'll write one coming out of this. Henrik raised his hand because he's like, he's like, dude, we like wrote the book on scale. He knows, he knows what he's talking about. But so scaling with Argo CD and with GitOps, the approach that Adobe is taking takes advantage of a lot of the structure that GitOps provides and directory structure and pull request generators from Argo CD and those kinds of things. So it has really great primitives for scale. But when is Argo CD going to run into performance challenges? What are the security considerations that we need to make? And then are there any organization structure considerations that we also need to take into consideration? There's a blog that I put together about this called Scaling Argo CD securely in 2022. This is a blog that I try to keep evergreen with what's happening in the community and anytime we learn something new or anything like that. And it talks a little bit about some of the approaches that we're going to talk about today. So one of the main considerations as people are planning to manage a fleet of clusters is if you should go with the hub and spoke model, that's one Argo CD instance managing many clusters and the other is a per cluster model. Should I have an Argo CD instance in every cluster? This is especially popular with edge deployments where a cluster needs to be able to operate independently with potentially bad networking conditions where things might get pulled offline or whatnot. And a per cluster approach is also favored if you're doing an air gap instance. So if you have somebody that needs to walk a repo update with a thumb drive to some secure site or something like that. So both of these approaches have their pros and cons. They both have their use cases. And sometimes I hear people debate them in terms of which one is better ultimately, which doesn't really make sense because it's really based on the situation. But at what point would you need to split up a hub and spoke because you might need multiple, right? It's not just a matter of having one because in Adobe's use case, you've got thousands of developers, you're onboarding more, and you have these additional partner development teams you have to support. So there's not gonna be a situation where you're like, we're just gonna run one Argo instance for the entire company, right? That's not gonna happen. So to benchmark Argo CD and first of all, there is a really excellent documentation guide put together in the doc. There's excellent documentation in the docs folks. And it's in the operator manual under high availability and it goes through and explains all of the components of Argo CD and how they scale. And it also explains why you would use a number of these things. So what we want to do is look at these use cases but then also compare it against real benchmarking data. So to do this, there's actually a tool hidden in plain sight in the Argo CD repository. There is a folder called hack. And under hack, there are a number of tools that we use to do benchmarking and performance testing of Argo CD. So when we make changes to Argo CD part of the automation, we actually spin up resources and check to reconciliation times and things so we can just make sure that performance isn't impacted by a particular change or we can understand that change. So under the hack folder, there is a tool called generate resources. And you can see an example of it running here. And you can specify generate X number of applications, generate X number of clusters, X number of repositories, X number of projects. And each of these points hits on a different component of Argo CD's scale. So what it does is in this case, this would be set up to spin up 200 V clusters and then assign 7,500 applications randomly across those clusters. There's another tool within hack called simulator. Simulator is essentially a chaos engine. It simulates a really bad set of developers who are going around and deleting stuff. And so you can spin up simulator and it will go around and mess with applications and trigger reconciliation and synchronization. So you can see an example of me running it here onto the side and for planning for Adobe, we actually wanted to scale up and find the breaking points up to 10,000 applications and up to about 200 clusters. So you can see the plan here. Now with Argo CD, the main thing isn't applications number, it's actually the number of objects that are being managed, Kubernetes objects. Because for each object, we have to reconcile that from at CD and that takes memory and it also hits the Kubernetes API and so this takes additional overhead. So this was the testing plan and here's a screenshot of Prometheus reporting over 10,000 applications and going through this exercise, we were able to look at all the different breaking points that we might encounter. Now I'm not gonna go through all of them. Now, when you install Argo CD, there are two flavors. There's Argo CD and there's Argo CD HA. There's actually more flavors than that but Argo CD HA replicates Redis and provides the replication capability and scale capability that we're gonna be wanting to look at. So some of the things, for example, that I ran into, once I got up around 7,000 applications, I started to have issues just with my browser loading the dashboards properly just because there are so many objects in memory that my browser was having a hard time keeping track of it. As I moved up from 1,000 to 2,500 applications, I noticed that my mean reconciliation time started to creep up and my reconciliation queues started to go up. Now this is very solvable. There's actually settings in Argo CD that you can use to actually solve all of these problems. So my reconciliation queues increasing means that it might take a long time to get back to an application to synchronize it. So as I increased, you might get into a situation where you're waiting 10 or 20 minutes for an application to synchronize if you haven't tweaked or managed these settings properly. So this gave us a good baseline of some of the breaking points that we might hit. So this is a very incredibly conservative slide. I would view this as a potentially controversial slide. I feel like some of the other Argo maintainers are gonna come and yell at me about this afterwards, so we'll see. So this is very conservative because if you're planning to support 40,000 developers or something, you just wanna have a benchmark in mind of what should I expect where I just don't have to touch anything and I'm just gonna know it's gonna work and at what point do I need to start thinking about that scale aspect? Yeah, so that's a pretty good starting point then, I guess, if you're out of the box. Because like I said, I'm trying to scale but cost is one of the things that I'm thinking about as well. So from that angle, I think it's always a better approach to take that conservativeness and then just grow into it as you kind of get some metrics and modeling like hey, this is what our patterns look like. Yeah, the 1500 app line here is really based on the fact that most people have more than seven objects in an app. They mostly have 100 objects or 200 objects, so the object count is really the driver there. 15,000 objects, you're gonna be very safe, you're gonna feel very comfortable, you're not gonna be really running into any issues. 50 clusters, you're not gonna have any issues. If 200 developers are running around and doing stuff all the time, you're not gonna have any issues. So this is a very safe benchmark. Now with tweaking, we can go far beyond this. Now, when I talk about going beyond this, I'm not talking about catastrophic failure. I mean, when I was running 10,000 applications, they were synchronizing. Sometimes it would be slow, sometimes it might crash and restart but it would pick up and run again, so it was fine. So it's doable, it's just a matter of tweaking it so you actually have a really good, reliable experience. So this is the part where I get kind of curious about because it's an area where I'm kind of challenged at. I have workloads that require isolation but thinking about how much do I have to, how many Argo Studio instances do I gonna need to kind of support these environments? What would you find like the security side of it? Yeah, one of the interesting use cases that you have is that you need to support not only multiple VPCs, which means I'm probably gonna have multiple Argo instances because I don't wanna punch through firewalls in most of those cases, they're VPCs for a reason.  Now the partner one is an interesting one and it's one that most people aren't aware of. Argo CD multi-tenancy is very good and we have done an incredible amount, we started SIG Security about 18 months ago and we've been focused really heavily on security within the Argo project and we are actually one of the first projects to pass 100% on the CNCF sonotype metrics that was accomplished last week and they came and gave us a big badge at our booth and stuff and there was lots of high fives but the multi-tenancy should be understood in the context of an organization. You are with Argo CD, you're telling people add a repository that contains arbitrary code, execute manifest generation, that could include customize, which is referencing additional external repos and it also includes things like JSON, which is like a full programming language. So you're saying add arbitrary code, execute arbitrary code on our space. Now we've done a lot of work to make sure that it's very difficult to do things like grab secrets from the cluster or output those things and there's a lot of guardrails to protect that and so it's considered very safe within an organization for you to use. However, we would not put an Argo CD instance out on the internet and just say here's multi-tenancy, everybody can go deploy to our namespace and this is actually something that came up for us at CodeFresh because part of our offering includes a hosted Argo CD instance that is on every account, every account gets one and so for us, we actually also took the vCluster route. We spin up a vCluster for every new account and we put Argo CD on it because while the RBAC is excellent, we don't consider the RBAC and as a project, we don't consider Argo CD safe to use in a public multi-tenant environment like that. So where you have partners, that's gonna be an impact. Conway's law generally prevents a lot of people from running into these issues early because one team is spinning up an Argo CD instance another team is spinning up an Argo CD instance and as many organizations mature, they're gonna start thinking about okay, how do I make sense of all of the instances that are running? This is a good time to start thinking about something like a control plane. In the interest of full disclosure, this is something that CodeFresh sells so I'm not gonna make a big sales pitch to you but it allows you to manage and track versions of all of the instances. You can have a single UI for all of your applications and all the clusters. You get better security isolation because the cost of it splitting up instances is lower and then you just have better resiliency and lower blast radius. So it's something to think about as you expand up. Some other considerations are most people move to a two repo model. Once they use Argo CD, that's something we recommend where you have application repos over here and then you have your GitOps repo or GitOps repos that is defining what should be deployed and that oftentimes means that multiple teams are operating in the same Git repo which is not something that organizations are used to and so that's when something like a code owner's file becomes very valuable. Code owner's files allow you to set permissions within a Git repository based on folders. So you can say this team can deploy to, can add stuff to that folder, this team can add stuff to that folder and that's something that most organizations aren't familiar with. Open source organizations are very familiar with it because we've been using it for a long time but it's something to consider and then also getting GitOps certified, there is a training for this that you actually certified. I did your first one, the second one, I think I got 93 right, I think the, 93%. I'd like to see you. Excellent. Most people have to retake the second one. I didn't tell you how many times I did. Four or five times. So this is currently free at learning.codefresh.io so it's worth grabbing, it won't be free forever. So what does all this mean for Adobe? If every pull request is generating a cluster, it means that we're gonna need to replicate the Argo CD app controller. This is a built-in feature of Argo CD to help you scale. It's basically a stateful set that is going to divide up and shard how we manage all of the clusters and the reconciliation. For the scale that we're looking at over probably the next year, this is gonna be very sufficient for what we're gonna be doing. As we go beyond that and we're supporting potentially above thousands, potentially getting up to like the 10,000 different environments range, we might wanna think about actually splitting up instances into multiple at that point. If every cluster generates a PR and we also have an app per cluster, we need to keep an eye on object counts. If you try to run a thousand objects on one application, you're probably gonna have some reconciliation challenges. So to solve this, it's good to use an app of apps pattern where you basically split up the application into multiple components. And this has other advantages because you can do things like say, this app synchronization needs to be complete before this app synchronization is complete. So you can actually do some dependency management if you need to. Ideally with get-ups we try to avoid those, but this is the real world. So who am I kidding? The other thing is supporting these partner orgs means you're gonna have to split up Argo instances because you're gonna want that better isolation and prevent any noisiness going on. Yeah, I think Conway's Law is helping me right now, but I do see there's some opportunities for us to kind of rethink where we're going with it. Yeah, and so that might be a point to consider something like a control plane. Yeah, so this kind of really means that, we kind of have a plan, we have this fleet in motion, and so looking at these numbers, we know there's some opportunities and a lot of strategies that I think a lot of us can kind of leverage and take from there, but as far as where we're going with Argo CD and that infrastructure, at least there's kind of a plan to know how to scale this. And trying to do it, like I said, cost efficiency is always a thing as well and security. So keeping those in mind. You may not know this, if you've been paying attention, Adobe has been speaking at this conference, most of the conference, this part, this talk is actually part of the greatest KubeCon quadrilogy of all time. There is an Adobe Cinematic Universe happening at KubeCon. Is C-Grips the prequel? The C-Grips is the prequel. Well, there's a whole prequel series from GitOpsCon. So there's even a prequel from there. So check out the extended universe of Adobe Talks. We've got a whole bunch of resources that I'll put these slides up. These will be uploaded into the scheduler by the end of the day and I'll tweet a link. And then you can follow me at today was awesome. Yep, Claude Takeru. And if you have any questions, we'll be in the hall. Thank you so much. Appreciate it. Thank you.


NEO to 34.  BIIB went all the way back down. We talked a little bit about this yesterday. Some of you guys are talking about Samsung and possibly buying them out. You know, like I was saying that it didn't kind of didn't make sense a little bit. So it came back down. They came out with a rumor saying that, you know, that didn't happen. So, a lot of things are looking kind of toppy today in the market. What's up, R.B. Nicco? I thought you caught, I thought you caught the COVID for a second there, man. Hope you've been good. Target's been moving nicely today to 31. What a move. Hasbro, strong move as well. Twitter, Viacom, 10. Very nice, very nice. Congratulations on that long-term hole. I think that I think some of those value companies are going to see some rotations into it. There's a lot of change in terms of narrative. There's a lot of change in terms of narrative of rotation from tech stocks to like consumer staples. So there's also a lot of talks about how Johnson and Johnson can be a good opportunity. But a lot of these health sector is starting to get very, very overbought now. So, I don't know, with the obsession of this, obviously, can we go over how PayPal has correlation with Bitcoin and how the next PayPal year can be influenced and how Bitcoin does? I'm not sure. This is Young Bo. So, PayPal, so Apple is looking a little bit red as well. Apple, Microsoft, the big guys are looking kind of red today. Amazon, what a trap this morning. Google, Tesla, everything is looking kind of red today, especially from the big guy's side. I don't know, is this the reversal? Is this the calm before the storm? Damn, so many alerts popped off today. Is this the reversal to the downside? Are we about to go? Is this going to happen? Find out next Monday. But let's see, PayPal and Bitcoin? So, we got PayPal on one chart here, let's pull up Bitcoin on the other side. Do we have correlation? All right, so we're looking at the one-day chart for PayPal and we're looking at the one-day chart for Bitcoin, right? I'm not sure if we have much correlation right now, but I know that in terms of earnings, we will see some correlation, depending on where the Bitcoin price is for the season and for the whole quarter. It's going to influence the earnings a little bit on PayPal as well because PayPal is holding a lot of Bitcoin themselves, so they're going to report in February, and when they report in February, they're going to report the previous quarters holdings. So, I guess anytime from last quarter, the previous quarter to the next quarter, whatever that Bitcoin price is, if Bitcoin is doing extremely well and doing really, really good, and it closed really well for the quarter, then the average price of the earnings is going to look well for PayPal. But if Bitcoin doesn't close well for the quarter, then it's not going to look good for that earnings report. I don't know, man. Bitcoin's looking kind of fishy here. Looks like it kind of want to die. There's a possibility of a head and shoulder set up here on Bitcoin too, looking at this shoulder head and possibly another shoulder here. If that happens, ugh. I would hate to see this, honestly. I don't think I'm ready for that drop yet, so hopefully that doesn't happen. Let's go over SPY for a second. So, the S&P 500, looking at the SPY Futures, which is the ES index. Looking at the half-day chart, we hit the double top here for today. We hit the same top that we touched on, the 28th. Struggling to break above it, so we saw some weakness and really really really dropped toward the end of the day, so sold off pretty hard. That's kind of like signaling some type of resistance, so kind of like when you're looking for support, right? Anytime, if you've been training for a while and you want to look for a reversal setup, you want to look for support where the stock is finding a bottom, like it is over here, it's finding a bottom, and then it reverses and goes back up, right? So right now, it's finding a top, so that's what's been happening the last few days. It's been finding that top. If you struggle to break above it and then keep hitting that resistance and it doesn't break above it, it's building that top over there and that means there's a good chance it's going to reversal back to the downside. So that's what we've been seeing the last few days. We've been seeing some resistance coming up here, which is good. I mean, but then again, I also have some various bias as well. How does the market usually look like in the first week of a new year? Is it bullish? That's a great question. We can check that out, but just remember though. Just remember, I know a lot of people are getting into like this whole talk about seasonalities and things like that, and I've said this before. Remember this, just because it snowed the same time last year doesn't mean it's going to snow the same time this year, right? So, you know, just because there was a big hurricane that happened in, you know, at the same time last year doesn't mean we're going to get the same type of hurricane this year. So just remember that a lot of these things are somewhat coincidence as well. So don't take it as like, you know, the true faith of things. But looking back at the beginning of 2021, wow, I can't believe it's already going to be 2022, man. This is crazy. Goddamn COVID, man. I don't even know what 2021 was like. I felt like I did nothing this whole year. So last year, in January, we did have a little pullback. December 31st was a big up move, and then we had a nice little pullback on the first two days of the new year. 2020, let's look at that. 2020 was a little bit chop, but the month of January was bullish even though the first few days of the year in 2020 was choppy. Same thing with over here. The month of January was pretty bullish until the end of the month. So most of the beginning of the month was pretty bullish, but it was choppy the first few days. So same thing happened over here. 2019 was not so good. 2019 was actually very, very bearish in December.  Then 2018, January was the first few days of January was choppy as well, and then we had a huge run and then bam, huge crash at the end of January. Got your booster shot today. Nice. Did you get $100? My friend said he went to get a booster shot yesterday. He waited online for like six hours just to get like $100. And he got like he got like four bags of like free beans or something like t-shirts, hoodies, or in like, I don't know, beanies and whatever. Yo, I got this, I got this vaccine shirt. I don't know if I can find it. I got this vaccine shirt. It's so, so ugly, man. So ugly. Let me see if I can find it. They don't have it online, but it's something like super ugly, man. I gotta find it. I'm gonna find it. My aunt gave it to me.  As she said, none of the kids want to wear it. So she gave it to me and I looked at it. I'm like, yo, I can see why they don't want to wear it.  It just says, I got Vax and so should you or something like that. I was going to wear it to gym just to troll people because everybody at the gym was like, just like super anti Vax. So I was going to do that. That's the only reason I got it just to try to take it to the gym to troll them. So yeah, we're just looking at spy before. We think this is the possible movement for spy. It's been struggling to break the resistance. So if it doesn't break 480, it's probably going to come back down a little bit. If it does break 480, we're probably going to see new highs. We just spent the last few minutes looking at the last three years of spy. Two out of three of the years in spy, the first week of January, the market didn't move that much. So it's very choppy. Let's check out Neil. So you guys didn't get the, you guys didn't get free t-shirts nor did you get like free $100 in New Jersey? What about like a free COVID test? So Neil had a really good trend line recovery here. So it's also setting up this nice little double bottom pattern. Damn, you guys got nothing for free in New Jersey. Hey, at least the shot was free, right? Yo, you know what's funny? I was watching, I was watching Seinfeld, Seinfeld last night, Jerry Seinfeld last night. And it's like a super, super old like sitcom slash comedy show or something like that, right? And one of the episodes, I just realized something like really, really common right now. One of the episodes, this one of that one of the characters Elaine, she's talking about how she's, she's, she's so torn up in terms of abortion, right?     Later she dates this hot guy and she dumps the guy for being pro choice as well. So I feel like, I feel like right now, this vaccine battle is at this point too.  Like I would not be surprised honestly, if, if there's probably already a choice set up in the dating apps, where like, is like pro vax or, or, or like, I don't know, anti vax or like, pro choice, right? It would be like pro vax or pro choice, right? And I was just thinking, man, if Elaine was living, like if she was doing the episode right now in 2021 or 2022, she would probably be like pro choice, right? That wouldn't that same concept apply?  Instead of all these mandates and whatnot. But I would imagine like people would just probably break up with the significant others if they weren't on that same page. That would be so funny. What do you guys think?  So they already have this then. You know, how funny would it be though? Like if, if like people still end up matching people for that. I feel like I should just make an app. I should make a profile just to say that I'm vaccinated and then and then troll people that should make an app saying I'm vaccinated and then I'm going to go troll people be like, you know what, I'm actually not vax, but I did it just so I can match a few. I mean, that's a whole debate in itself, man. Like, um, like, it's, it's, it's not just about like, you know, it's tricky. It's a tricky conversation to have. I actually don't want to get into it because we can go on and on about this. But let's go back to Neo. Let's go back to Neo. Oh, this is like, that was one of the earlier episodes where George is like, George is like, come here. He's like, I got this. I got this good tip on this stock. They're about to make like this, uh, like some automated burger chopper, you know, and then, and then like, um, and then, and then they get into the stock and it's like some penny stock where it goes up and down and they're like, it messes up Jerry's whole week. Yo, yo, actually that's a, you know, that's kind of, that's kind of true. If you think about it because the episode was really realistic because for some of us, man, um, I don't know about you guys, but I don't like for most of us, um, a robot butcher, yes, that's what it was.   You know, he went to the cabin, um, or whatever. And, and dude didn't get laid that week. It was just bad. He got fun. That's true. He got fun. He got fun. And then he lost. And then the girl was like, yo, why didn't you diamond hand it? He got so mad at her. Yo, my man probably didn't even get laid that weekend either. Yeah, that's true. That's true. Oh yeah. He was looking at the newspaper. You know, times are so different back in the days, man, when you're like the way the only way to check the stock price was looking at the newspaper, bro. Can you imagine if you guys had to deal with that? Like if you, if you had to live your day, like where you can only check the stock like once a day by looking at the newspaper, like what, what is life? Damn, man. You can only see the opening and the closing price. He says, I told you this market fluctuates. He says, of course the stock market fluctuates. Everybody knows that. That's so true. Yo, what's up, man? What's going on? That's good. December has been a pretty slow month. A lot of low volume, but yo, for some of the people that has been fortunate enough to be in it, Spy had made a great recovery. We're looking at Nio's right now. We're looking at Nio, and Nio looks like a double bottom setup possibly. So we could see a recovery to 34, 35 maybe, if we can break this resistance over here. So we need to break over that purple line. If we can get over that purple line, we can possibly come back to 35s, maybe even as high as 37s. But who knows? The market just dumped pretty hard. So it's kind of iffy right now. The market just dumped really hard, but the China sector ran 10% today. Why is that? That's weird. Yeah. I mean, look, if we can break above this purple line right here. So this purple line is 3288, right? So if we can open above 33 tomorrow, we can easily run more. But the market right now is looking a little iffy. So for tomorrow, we would need Spy not to drop as much too. So we would need Spy to continue to chop and just kind of stay in that range if you want Nio to go a little bit further. I mean, I'm with you guys, man. I want to see that Nio run because I'm in some LCID, Lucet. We played this in the challenge account. We were looking for a breakout last time when they got added to the NASDAQ. And they've been chopping for so long. They've been chopping since December 20th. And now it's almost December 30th. That's 10 days of chop, man. Stop chopping and start running. So we've been waiting for that move. Got some $44 calls that on the calendar play. So the premiums all burnt out. We got into that play like a week ago. So we got five days of premium burnt. Now we just need this to move back up to $44. And if we get that move tomorrow, everybody's going to be doing well. Congrats on those Nio leaps, man. Good play. What's up, fly guy going on? Yeah, honestly, dude, when I used to see Seinfeld as a kid, when I was younger, I used to see it on TV. And I swear to God, I have no clue what that show is about. Like, I could not understand it. Same thing with friends. When I used to see friends on TV, I used to watch it and I'm like, I don't understand, man. I had no clue what it was about, right? Hold on. Let me get this call. All right. What was I saying? Oh, yeah, Seinfeld and friends, man. When I was younger, I couldn't understand it. Like when I was a teen, some of the stuff that like some of the stuff they talk about, you have to kind of be old enough to understand it. Like, like, for example, I just watched this episode. And and like, and there was this episode about where Jerry was dating a gymnastic girl, right? And they're like talking about how like, they're like creamer comes into the apartment to show like to show him this video of her performing the Olympics in Olympics, right? And like, I imagine they're probably talking about how like she's so flexible and she's doing all these moves and things like that. And they're like, yo, you gotta, you gotta date her. Jerry's like, I don't know what I'm going to talk to her about. They're like, you gotta, you gotta date her. She's like probably such a great lady, you know, like they're like trying to convince him he's gotta do it. They're like, yo, the sex gotta be like the best.  Like what the hell and George, man, oh my God, this guy, you need spy to hit 45 by January 3rd. I'm telling you now, man, you got to roll that. I don't think it's going to hit it by January 3rd. You might have to roll that out to next week after that. I know, right? Wait till, wait till you see friends, man. Friends is so good too. When you watch it like at like in your late 20s. Oh, they actually just opened like a new friend store, I think in New York called the friends experience. And that seemed like pretty cool. All facts. George though, I don't understand, man. I don't understand how this dude pulls any girls. Like, I mean, I understand in the later season how he was able to pull girls, but in the early season, man, this guy, he should be a simp. Like he should be like he should be like on his knees begging, bro. Like this is like George is like one of the most selfish characters I've ever seen, man. Like for a guy that shouldn't be pulling these girls. He's one of the most selfish characters I've ever seen. Some of the girls he breaks up with is just ridiculous, man. I still remember this one episode where he became where like they got the deal to to write the sitcom. And and he's like, what was it? Oh, he started hitting on the girl in the bar, man.  But now he can finally get girls like come on, dude, like you got to be humble, man. Like it's like kind of like Jeff Bezos, right? Like Jeff Bezos only became so successful because of his wife. And now he can probably like practically get almost any girl in the world, but he wouldn't have done it without, you know, half her for help. But guys are like that, right? All right. So Lucid, we're looking for a recovery move back to $40 tomorrow. If that momentum in the car sector continues, I think China also has some pretty good news or the CCP. Somebody said it earlier. CCP says something about lowering taxes. Oh, you know what? I just realized you guys are talking about tax harvesting, right? What if what if all the hedge funds that were shorting the China sector decided to cover their short positions today? So if they were trying to cover their short position today, right? Then then they have to buy back shares. If they're buying back shares that's driving on volume. And that's probably why it's making the whole the whole China sector going up. It usually does take like a take time to settle. But if they're covering the position, it's going to start showing up, you know, people noticed it like two days ago, actually, beefy. I don't know if beefy is here. He actually messaged me. He was like, yo, I see some weird flows on like Alibaba or whatever. So maybe like they were already doing it. Let me see. Let me see if I got the money flow signal a few days ago or not. So we got the money flow signal. No, we just got it today. I don't know, kind of sus. The movement is very sus. It almost seemed like a trap in the way the way the way we're getting that move. Honestly, GOTU. What is this? Do some crypto? Wow, what are we covering, man? It's probably a good area to start selling some like cover calls. If you guys own these shares, it's probably a good time to start selling some cover calls against it. Be right back, God to God. CCP did say something about I don't think it was just about lowering taxes. I think they also said something about allowing more money to invest into the EV sector as well. Let me google the CCP EV sector. Actually, I can't find it. I saw it like a day ago, but I can't see the article. Damn, I don't know where I saw it, man. I can't remember where I saw it. I don't know if I was looking at NEO when I saw that. If I was looking at something else. But just be careful, though, guys. Don't go too big into these positions just because they're starting to get really hype. Because anytime when something run like this much, it's usually a trap. Because we have seen this before. We have seen this happen quite a few times. You know, like look at these big moves, right? These big moves usually want to trap more people coming in. But like over here, big move trap. So look for that pullback before you go in for it. You know, you want to try to load up on the bigger position. Because anytime you see big move like that, it usually doesn't really go anywhere. So right now you might be feeling like super FOMO. Be like, oh man, it's already at $33. It's going to hit $35 tomorrow. But ideally, you want to wait just to like over one to two weeks out for that $35 move. Because having more time never hurts you, especially when you're playing naked options. What else are you guys looking at? Damn, look at Wall Street Med. Look at hella sexy. Whoa, whoa, whoa. They got Asian guy at Wall Street. What was this? What do you got that's expired in tomorrow? Has anybody used these soap? I saw like this really long commercial on the Sasquatch soap. But I don't know how good it is. It's like $7 of bar, yo. What is doctor? Deodorant? Oh, oh my bad. That's the site. What have you gotten from there? You have you gotten the soap, the whole bundle, the deodorant, the toothpaste, the hair care, the shower booster. What is the shower booster? Scout, scrubber, travel bag, soap booster pack? Wow.  They're so expensive, man. Who is buying these stuff? What options do you have expiring tomorrow? I wonder what pine tar smells like? Oh yeah, everybody was hyped today. Nancy bought some roadblocks. $100 January 2023. Let's go. Time to ape into it. So they got Nancy's filing today. What did she get? What did she get? She got 10 options called with a strike of 2000 for Google. She picked up some MU. She got some MU purchase 100 call option with a strike of 50 with the expiration of September 2022. What is this? AB? Is this that bank company? Yeah, it's like some bank company that her friend worked at. I remember seeing this before. She's gotten this this company before. AB, I remember she picked some up last year, like all the way down here. So she picked up some roadblocks as well. Purchase 100 share options. She also got some sales force. Who doesn't believe in sales? You know, she's only buying calls. She doesn't buy puts because stocks only go up boys. Purchase 50 call options with strike price of 130 on Walt Disney. Let's look at these. MU, it does look like a double top. Yo, I drew it last time here too. Can't believe we actually hit it. So last time I earned it, I was like, yo, we're either coming all the way up here or we coming back down here to this super support. But it looks like looks like we're we've been moving up. I think we might see some pullback. Got dividend date coming up very soon. That 10 cent dividend looking a little bit weak here on that double top. So I mean, if market is bullish, we'll break through. But she got a lot of time. She bought a lot of time on these. I think everything she bought looks like, except for roadblocks, roadblocks look good. This is one of the only good ones on her list. So this looks like a possible double bottom setup. If we're bullish, we get a double bottom setup possible move back to 120s. What else did she buy? Disney and sales force. Check that out. Disney. The hell? We low key have them missing out on this. Look at Disney making this move here. Look at Disney making this double bottom move. Can it come back here? So our side is looking like a double top as well. But if market continues to grind and we were continuing to be bullish, this could potentially grind back to 170s, 168. I think we have some positions open for that too. So let me see. What is our Disney play at? Oh, 170 to 175. So if we're lucky enough, maybe it will come back to like the 160, 170 range. With this system, start some position a while back for it in our challenge account. So I might have to add another position, since it's looking pretty good here. Check out CRM. CRM is another interesting one. If we can continue this move, I think we can easily see a move to 270s. Let me check out how much 270s cost. Anybody in CRM yet? I know some people got into Roblox today. Working like a move to 270s. Let's see. Cover one week. It's week after. Probably end of January. I would say looking for a move to 270s. What is that? 255s right now. 260s, 270s. So if we think there's a possible move that could happen the next 30 days, going from 255 to 270s as a $15 move, if that happens, could potentially make anywhere from 60% to 300%. The longer it takes to happen, the more money we can make. Pretty interesting. So I need two weeks or maybe three weeks at this point for this move to happen. So I might set this up for our challenge account tomorrow. CRM 270s by mid anyway. It's a possible setup. We'll probably do tomorrow. See how market goes. If market continue to chop back down, we might have to find some bearish setup as well. Breaking news. As far as the build back better plan, old child tax credit will be paid in form of Roblox gift cards. That's true. It's Roblox, man. Any kids can tell you Roblox is a good company. Oh snap. That sounds crazy. This guy says he played Roblox as nine year old nephew of a girlfriend at Christmas Eve. The two games they play were SWAT simulator in which we literally beat non-violent protesters holding signs to death from the comfort of our riot shields and Zulu wars in which we create the battle of the Rokers Drift, masquerading waves of natives with spears with our breach loaded rifles. Best up. Has anybody here played Roblox and RDS? What's up, Nick? What's going on? Oh wow. When did this IPO? I forgot about this, man. I don't know, man. I like the company. I would never imagine it with IPO, but hey, look at it now. Here it is, right? I don't even know how this company makes money. I imagine they probably make money from ads and stuff. It's going to be interesting to see what the earnings look like. It's hard to kind of gauge what the price point is at the current price of where it is at right now. I think by earnings we'll probably have a better idea to see what the price-earning ratio is to get a better how the sales revenue is compared to the previous years. I'm sure if we go on the investor's page on the website right now, we could probably find the presentations and stuff and what their projections are, but sometimes those are overstate as well. Let me see these price targets. Are you big on that stock? Some of the analysts say they're thinking it's possible to see it hitting $35, $29, $40. We'll probably get an average of Morgan Stanley thinks it's worth $24. Just keep in mind though, I know a lot of people when they see these price analysts put these price points down, they take it as if it's going to happen really soon or tomorrow or something like that. A lot of times when they have these price targets, they're throwing out for like a whole year, man. A lot of these price targets, they're looking at a year out. They're not looking at like right now, right now, but a lot of people don't realize that and they just like jump right in. Let me see, when did these price targets came out? November 29th? What was it doing November 29th? The stock was crashing. It was crashing on November 29th and that's when they started releasing these price targets. Oh, you know what Nick? The other thing you should check out, look for if you're investing in these new IPOs. One of the most important thing you should check out is look for when the lockout day is, right? Because you want to put that date on your calendar somewhere if you're trying to buy the dip right now. You want to make sure you have that date somewhere of when the lockout date is. So because that's when all the other early investors are going to have the opportunity to unload and you want to sell before that and you want to buy in after that date. But sometimes they make a run right before that date because the hedge fund has the responsibility to drive that price up for their investors. So they usually make a run before that date happens. So if you're putting options, those are some good dates to keep mine up. If you're creating shares, you can also sell options against it during those dates when it runs up a lot. Let's check it out on the chart, see how it looks like. I hope that helps, man. So it's in the tight zone right here, so we've been chopping. So if it breaks out from here, this could potentially be the reversal. Next target would be 22s. If it doesn't break out from here, it's probably going to come back so you could look for that $14 area to buy the dip, probably put a stop loss around $12.50 or $13 and then look for a small area to sell back around $15 if you're buying at this $14 area and then you hold the other half in case it runs back to like $21s, I imagine. NRDS. That's the wrong link. Let me send you this link. But that's it for today, guys. We'll be back here tomorrow, Friday, New Year's Eve. So we'll be back here tomorrow. We'll look over some more stuff and then hopefully next week we'll start the earnings challenge and we'll get the accounts running again and hopefully we'll start making money for the new year. But thanks for stopping by and hanging out with us, guys. Take care and have a good night.