Tastes like wasted opportunity Hey guys welcome to another episode of ten years old today the show where I talk about movies that are turning ten years old And I take you down a little trip down Nostalgia Avenue today's episode is about Jumper a movie that was released on February 14th 2008 It was based on a 1992 novel by Steven Gold the film was directed by a claim director Doug Lehman He was written by Simon Kenberg Jim Ullis and David S. Goyer This frickin hack. This is when I really started to see how much of a shitty writer David S. Goyer was It's pretty interesting that Simon Kenberg basically the man who is really behind the writing for the X-Men movies as a part of this But Goyer Jumper is a wasted opportunity of an extremely interesting concept Everyone always has that conversation about what superhero power would they want to have whether it be invisibility incredible strength the ability to fly This movie is the one that really convinced me that the one to have is Teleporting especially from the trailers the trailers were so Intriguing the idea of being able to literally go anywhere have Unlimited wealth but then also be hunted down for the power that you inherently have and admittedly throughout the film the concept Of teleporting is constantly used in an intriguing and very cool way The effects in this movie are pretty darn good. If not, they actually still stand up to today However, there's one really big issue that kind of angers me in the trailer that was first released for this movie They show that every time Hating Christensen was going to do a jump. It would always make this noise Now admittedly hearing that noise every time would have been super annoying but in super intense parts It kind of would have been cool instead all it does is it just makes this noise Now I'm not saying that hearing the rule all the time would have been cool But it just kind of ruined it for me This was my first interaction of a trailer giving you a false impression of a movie as well So there's a lot of nostalgic feelers to this movie My friends thought it was all right But I just saw through all the holes in this movie one of them being Hating Christensen's absolutely horrible acting through this movie He really doesn't do a good job.  Samuel L. Jackson is kind of cool There is an interesting idea about what are consequences when you have such powers, but they never really delve into it They're supposed to be a war, but you only ever really see Frickin Jamie Bell and Hayden Christensen fighting dudes with these weird grapple gun things another thing that this movie actually introduced me to was that weird Aqua and yellow warming color Ratio thing that's used on posters to kind of drag people into it It's been used for movies like I am number four. It was used for Mad Max It's just this kind of color template that is the most appealing to people's eyes And this was the first time I ever saw it in a movie trailer or a movie poster There was also a really crappy ass game that was released with it. I never played it I wasn't that desperate for a chief ends, but I do know some people who played it It was apparently an easy thousand, but they said it was a piece of garbage either way Jumper is a wasted opportunity that was really hindered by Hayden Christensen David S Goyer's shit-tastic writing and just some really stupid garbage thrown into this movie It has an incredibly in-depth concept and of idea that I wish Had it been handled by different people might have been much more of an interesting idea hell This could have been a really cool TV show or mini series It's actually spawned a lot of fan films and a lot of people who are getting into film and testing after effects and whatnot To test it out themselves So this movie does have a placeholder for reasons that are not really the movie's main reason The movie was supposed to be successful and turned it actually just gave a lot of other people ideas to try and do their own Little short jumper movies so in the end jumper is a piece of garbage But it's a memorable piece of garbage because of its interesting concept and just Really showing that teleportation is a pretty cool power to have Anyways guys, thank you for tuning in to another episode of ten years old today. Let me know what you guys think of jumper Did you like this movie? Did you play the game? What were your thoughts about it? If you liked this video leave a like down below and if you're interested in more maybe subscribe Anyways until the next episode. I'll see you guys later


Hey y'all, sorry once again We got one thing to do actually a bit of a randomizer this Jackson Holiday and tomorrow Johnson Prime Perry's dual auto Going for either the Orioles or the Pirates So Kevin and Ed would switch screens. Sorry y'all. I am a Dumb first break of the day. We're going to go Baltimore and Pitburg Pitburg let's roll our dice and randomize six and one seven times Kevin Ed good luck y'all one two three four five six and seven final time Pittsburgh Boom Pittsburgh on the seventh time. We'll get the dual auto tomorrow and Jackson Holiday So Ed Congrats Come on Chris Just because it's your Friday doesn't mean you can start slacking So switch screens one more time the Jackson Holiday tomorrow Johnson dual going to Pittsburgh All right, there we go. That's a break more baseball up on the site right now at chassis case breaks calm. Thanks again y'all. Bye. Bye


Yeah What I mean by this It's like this is We can go ahead and get started so I need the microphone You want to join then I'm gonna have you guys kind of pair up So hopefully you guys were able to watch the video and review the visual field anatomy So I'm not really gonna go over specifics of the anatomy Here's your chance if you didn't Or really technical aspects of Humphreys and Colomons and things like that But if you have any questions Ask me and I'll do my best. I don't really answer. I'll get back to you later So here's a normal goldman visual field these are normal blind spots for those not familiar with visual fields It's like you're looking out of the page as the patient and so what's on the right side is from the patient's right eye What's on the left is from the patient's left eye? These are the normal physiologic blind spots, which are around 15 degrees temporally of the point of fixation and normal fully All visual fields is about 60 degrees superior nasally 60 to 7 inferiorly Around 90 or so temporarily that would be a full visual field Teresa so we're kind of pairing up twos and threes if you want to join Maybe Rachel over here or whoever you want. It's fine Or if you want to Do all it on your own that's great to you Or you guys can make a group of twos either way So let's start with some cases. So this is Someone sends you this visual field. This is all you know about the patient What kind of things are going through your mind when you see this visual field all we have is this one Which is the left eye So you guys kind of talk amongst yourself Kind of come up with a clinical scenario for this what might be causing it. What else do you want to know about this patient? Brad and Chris kind of give us some thoughts on this so we said like it could be Partial arc you at defect or like a Seco central So we would want to know Like the age of the patient for sure Okay, I mean obviously any like ocular history do they have a known diagnosis of Very important never I might be helpful So let's say this is a 30 year old And let's say this is the right eye is normal. What's kind of your differential at that point? The right eye is completely right as normal 30 year olds So, you know 30 year old girl someone sends you this visual field. What are top five things that you're wondering?  So Let's say it's someone with in this is in both eyes What they what's your differential for our seco central scutomas in both eyes? Let's say painless You like systemic diseases Yeah So by a lot of optic neuritis Painless or seco central scutomas are concerning for nutritional deficiencies. So B12 types of C's Like if they and be tall things that give Optic neuropathies from medications Vibers saw in the differential for bilateral seco central scutomas so Lot of times we get really poor records from outside and we get things like this But this even just this alone gives us a lot of information that gives us a list of questions that we want to answer when we see the patient So this is kind of what gives a seco central scutoma. So it's from Disorder of the papillomaculobungal, which is right here The fibers coming right from the center of the phobia over to the optic disc. These are very Nutrient dense areas. So this is why things like nutritional deficiencies particularly affect this area and optic neuritis often gives us central scutoma Extending over to be a seco central scutoma again because they're very active Areas that are easily injured with oxidative stress So this is the example of a seco central scutoma So here's the case 19 year old man painless loss of vision left eye progressed over three days Three weeks later had no improvement in that eye, but then developed painless loss in the right eye So you guys talk kind of what's top on your differential on this case? I haven't really given you guys too many details, but Young guy otherwise healthy loses vision one eye painless Then not too long later. There's this vision the right eye still painless. How about you guys over here? Any thoughts on that? I have a knee jerk reaction to what you might be thinking first Here's his exam right eyes count fingers 24 in the left. No color. There's no APD. I movements are full You look at his fund is he has some peri-pepillary tilting ectasia We're hearing optic nerves and includes at this point these prizes and have APD because Yeah The so that keep that in mind and we'll talk about that in this case It's not surprising because it's bilateral, but Once we go over what it actually is reminding them Anyone else have any thoughts or diagnosis at this point Leavers. Yep. So young guy painless vision loss sequential rapidly sequential The other clues are the peri-pepillary tilting ectasia So the nerve can look pretty normal and kind of a full appearance, but you look around the nerve It's got these little tilting ectasias, but it's more of a pseudo-ladema appearance than regular than actual optic disc edema So what's the typical visual field visual field and leavers and I already talked about it So bilateral secocentral scatomas is most classic for leavers So this is what the patient had So going back to leavers. So initially when they present in one eye So if you had seen the sky when you just Had the problem in the whichever the first eye was and you didn't see a APD that would be very confusing because he was count fingers No color vision that I you're very concerned for optic neuropathy, but you don't see an APD So that's very confusing. You might think it's a retina problem. You might think he's faking which can happen, but It's for reasons. I don't think anyone really knows Possibly because the other eye is going to be affected. It's kind of in that pre-monitory phase But you don't see an APD and it's not unusual to not see an APD with that first eye that's involved Either it doesn't involve the ganglion cells in the back that contribute more to the APD or it's because that other eye is subclinically involved enough to not Allow for an APD So always keep the evers in mind when you see something. It looks like a bad optic neuropathy, but you're not seeing an APD Don't discount leavers in that situation, especially if it's like the classic young man with leavers Or with payments vision loss So someone how is the evers inherited? What is the genetic disorder for leavers? There's about three classic genetic mutations for it, but there's others being discovered Some mitochondrial leavers may not have APD initially Most commonly is going to eventually be bilateral after usually a couple of months in between their eyes Seco central scatoma. Here's another case so this guy So pay attention to these things so you get these visual fields which look terrible except for some sparing, but he has 2020 vision So what do you think is going on with this lesion this visual field? You know to see as a foveal thresholds are 30 on the left 39 on the right which goes with this 2020 vision What a theory I do that even if it was robust so your retinal artery probably would end up with 20 20 vision So so you kind of label it as constriction was sparing the macula. So where would you localize that you also already mentioned the retina can cause that Bilateral optic neuropathy is probably less likely so Retina or bilateral cortical like you mentioned are probably two most common so this guy is actually he was I don't know. He's about 40. He was Very sad story was hanging a flag up at a restaurant on Veterans Day like a year ago and fell off the ladder and Had a hemorrhage in the back of his head Went to the hospital had that treated and eventually Decompensated and was herniating and stroked out his bilateral PCA's while herniating stroked out his bilateral oxyprolubes So this is what he had he also became deaf at the time also, so doing a good deed and became Helen Keller, but So you see going back to the visual field. It's a little bit Not as bad in the left in both eyes if you look closely at his MRI it's Not as bad on the right, but this is a bilateral oxyprolation You can see it's sparing the tip of the oxyprolobes for the most part, which is why he has really good central vision So just to kind of briefly review so the oxyprolobes the most posterior part of the oxyprolobes is your macula central vision more anterior and the oxyprolobes is the peripheral vision so if you spare The poles of the oxyprolobes. You have the potential to spare your macula or your central vision Which is what he did which is among all the bad things one of the better things that happened to him You can see this is the contusion from this fall The vision loss is all from back here So here's just a cat scan cat scans are not quite as easy except for maybe our neurologist To read what do you think the visual field will be in this patient? Maybe let's go with our group with a neurologist in it See what what's wrong with the brain in this cat scan is it normal or is it animal? Which side is that normal Over here So actually this is the abnormal size see this dark so strobes that are Subacute to chronic appeared dark on cat scan for all you all the moment is out there So this side is normal, but you see this And hypodensities Terminal the terminology for it. That's Subacute to acute Chronic stroke so acute strokes first 24 hours look normal on cat scan So this one's a little bit tougher because MRIs are much easier to show things like this But I didn't have one on this patient, but so where are we in the brain? So this is the abnormal side Roughly, where are we? It's hard to on this let's say is the inferior occipital low where we are what is the visual field defect with that? so Left occipital because it's the right superior But this was her visual field so Right superior quadren's no pia monomous quadrant no pia From the left inferior occipital infarct So here's the case 27 year old woman. She's five and a half weeks pregnant Brad, you know this patient came with vision loss in both eyes One week and a headache What are you concerned about right now? What are you really concerned about and a pregnant lady with a headache acute onset? That's a good one. Yeah Venus sinus thrombosis So hypercretic will stay Had a pregnant lady So this is her exam 2020 vision has no APD probably is normal sounds fine, right? What else do you want to know for her? I mean, I would want to get a visual field on her You want to know what her nerves look like You know just send her home right now complaining lady These are nerves What's her visual field? potentially going to look like So first what's going on for all the non-optimologists in the room with her nerves a little touch at discotema So severe optic discotema both eyes So you guys talk what's the visual field defects most commonly with optic discotema from papillodema Common visual defects in papillodema That's usually the first thing to see what else so most mild with papillodema is no visual field change Blind spots are one of the first things we see These old depression is a very common one and then Then it starts to get constricted So these people often won't notice that they're losing vision because their acuity is 2020 until their fields get so constricted. So just relying on the subjective Nature the patient's vision is not great. You have to actually go check the visual fields formally if possible So I saw this lady in clinic and these were her visual fields She was pregnant So this isn't really an age talk, but we'll kind of go over a little bit. So she's pregnant. She's got these visual fields So you're worried or you're not worried about this patient. She's got severe papillodema I'll tell you she didn't have a venous science thrombosis. So she just has elevated pressure for no other reason Those with more experience with IH. What are you kind of? Thinking is your next step in this at this point. So again, not an age talk But this is vision-threatening IH that you have to do something more aggressive like lumbar drains possibly Finistrations if needed so She already had her MRI which is normal. Otherwise, opening pressure is 56. It's very high. Otherwise, he's that was normal So she was admitted for a lumbar drain to kind of temporize things drain the fluid repeat visual fields We started die-maps at the same time And then the plan was if visual fields didn't improve then do optinertiae finistrations So this is kind of a gradual progression of her visual fields. So first time I saw her left eye and right eye This is after lumbar drain or this is five days later And so you see improvement there improvement in the right eye So we kind of stuck with things with the diamox. She continued to improve About two months after I first saw her so luckily luckily for her she did okay with diamox so Always keep in mind vision-threatening IH that they have severe Visual field loss Then that's something to be concerned about and you want to be more aggressive of that with lumbar drains possibly optic Nerf teeth and illustrations things like that So just to review fields and IH so we're with papillodema in large blind spots nasal depression Diffuse constriction last thing that goes is the visual acuity Question about that doctor's seat. So this might be wrong too But there's a question that I just had that said what's the most common visual field defects seen in IIH They answer as partial arc you it With or without enlarge blind spot and then enlarge blind spot being the second most common Is that true experience? I feel like a large blind spot is most common, right? They'll make any sense What's the question from? I mean it says that it was I haven't looked up the study honestly, but it says this was what was reported in the IIH Treatment trials, so I don't know. I just didn't know I've never heard of that before Yeah, I don't know the board Collection answer to that in the experience is some large blind spot But but you see those are And that I see the nasal depression a lot also It's controversial depends on the center usually you can This Some people will do contrast some people won't and a pregnant ladies there's with the gadolinium think iodine is contraindicated, but There's no 100% contraindication to get though She was five and a half weeks pregnant on september 5th Because she was really worried I think about the acidosol yeah someone that recommended her diamox, which is Doesn't have great evidence that it's harmful to the baby, but there's In animals it's potentially harmful, but there's no real human evidence that is harmful. So some People are hesitant to take it, but she's been on two grams in september Her ob-gyn is fine with it. Most people are generally fine with it It's just kind of educating the patient that we don't have great evidence one way or the other, but A lot of cases are reported where there's no effect from diamox So here's the 33 year old woman had trouble finding birds in the sky Reading first parts of words seeing the mouse on the computer screen Slowly progressive. She doesn't really know when it started, but it's probably been a few years Things both eyes equally affected otherwise healthy. No family history of diamox So her exam so you can get to 2020 both eyes kind of eccentric vision Colors decrease both eyes People's equal. They're questionably a trace right APT eye movements otherwise normal So these are her optic nerves Anyone quickly want to say what they see with these optic nerves Disc margins look pretty crisp She has a normal cup-to-disk ratio if anything her Optic nerves appear slightly hyperemic But I don't see any optic disc power or disc margins. They look fairly healthy to me Exciting no answers yet for her vision So can you predict the visual field just based on her history? How do you guys kind of discuss what you think her visual field is going to be? Somewhere in the center Just having trouble finding little things So this was her Humphrey So you can see up here. That's can't I tell but down here you see the central lesion here central here Is it possibly more on the left side? So I got these little central scatomas to localize that can you go back to the visual field? Or sorry the golden trees that your group Localize bilateral central scatomas You said right side Yeah, but it'd be bilateral it's bilateral central scatomas Optic nerve could be possible too bilateral optic neuropathies can give you a central scatomas So OCT, RNFL is pretty normal So this is our OCT of the macula on ophthalmologist. This is through the phobia. This is a normal phobia old depression Any of you ophthalmologists want to say what you see on this? What's the uh The left side zone Right in the center So this is correspond with her visual field defects here Yep So she's got a retinal problem causing bilateral central scatomas. So she went to Dr. Bernstein ERG was actually normal that he's concerned for a cone dystrophy in her She's getting genetic testing So The neuro entomologist see right to things too Here's the case 15 year old girl was in a car accident a month prior to me seeing her Her complaints in her vision were just blurry vision at distance and double vision at near had headaches nauseas and neck pain Went to another eye doctor which told she had peripheral vision loss So if you Take out that last sentence that kind of sounds typical of a post concussion patient blurry vision Especially double vision at New York because they get conversions and sufficiency But since this is a visual field lecture Why am I she has some peripheral vision loss after a car accident? Is that A minor car accident. Is that normal or Is that surprising?  I move into normal And had some conversions and sufficiency Consistent with post concussion syndrome These were her optic or her fundus photos Which these are her visual fields So What do you guys think about these visual fields? How would you approach this patient at this point? Given these visual fields She I mean her main complaints were blurry vision at distance double at near it wasn't I can't see anymore I think a 15 year old girl who underwent a traumatic event. You always have to keep in mind functional vision loss So tell me about the tangent screen, what do you do with that? So when they move back you expect the field to expand It stays the same sometimes it gets smaller than that's highly suspicious for non-physiologic vision loss When you get a gold mine, you could do a gold mine too is another option And her gold mine is also concerning So she so 15 year old I was highly suspicious for non-physiologic I did a tangent screen on her sometimes she expanded sometimes she didn't Um, it's hard to really label people as non-physiologic though is post traumatic 15 year old girl I was thinking she was going to be normal But I got a erg which was abnormal And again went to dr. Bernstein And certainly she has right now is pigmentosa so One of the things that looking back made me Should have made me more Or less likely to think it was non-physiologic. She wasn't complaining of vision loss This was just incidentally found She was didn't come in saying I can't see it was just double vision at ear blurry vision And she's had this forever most likely so she's never really known any difference So it wasn't until more questioning that they kind of found out that our night vision was not that great and things like that but So always I really hate non-physiologic disorders because you get stuff like this when it's totally real when it looks Otherwise not So you have to be really careful before you label someone non-physiologic Or I forget so I forgot to make a quiz I'm going to make a quiz and email it to you guys So if you guys can just write your Email address and I'll email it later Now we just have some kind of rapid fire visual fields So I'll show you ones discuss real quick And then someone shout it out Just what the defect is where it localizes List this yeah, so yeah So like they only have the inferiorities. Yeah, so optic Nerve anomaly So it could be bilateral optic nerve problems causing inferior Altitudinal defects Could be brain also so posterior Superior occipital lobe cause that field defect Of this one with the visual field defect Except it it wouldn't be parietal be temporal or inferior occipital So this is just again showing the occipital lobe posterior occipital lobe For the central vision the macula peripheral vision is represented anteriorly. So this is a small So this would be you'd expect this to be more posterior occipital lobe given this small more central Superior quadringtonopia How about this one my central field defect the rights pretty much Not much vision there with a left temporal defect What's the name for that kind of visual field defect? If what's symmetric You don't know if there's a Well, we know that the right eye is severely affected which localizes to Anterior to the chiasm We know that the left eye has a temporal defect which localizes to Junctional scatoma. Yeah, so a junctional scatoma because there's a temporal defect in one eye and a Central defect or kind of diffuse optic neuropathy defect in the other eye So that localizes to the chiasm, but it's involving more of the right optic nerve than it is the left That's why you get so much involvement of the right optic nerve And it extends back to the chiasm and affects those fibers that cross and causes that Temporal defect on the left eye So this localizes to the optic chiasm A little bit more anterior in the right optic nerve though So you think of things like tuotary tumors any optic chiasm lesion How about this one right parietal and right superior occipital Anterior to the chiasm anything It's to kind of done this before but as a repetition So This visual field defect plus a right apd So what's the visual field defect? You know, yeah as a right apd Is that weird? That is functional visual That one more time did everyone hear that? So this localizes to Left optic tract specifically Because So that's exactly right so our temporal fields are bigger than our medial nasal fields So there's an over representation of that temporal visual field. So there's more fibers from that From the medial fibers that cross So the optic tract has an over representation of the contralateral eye So when you take out the optic tract, it's still asymmetrically involving that contralateral eye Which is why you'll get an apd. It's usually not a huge apd.  It's probably an optic tract lesion Let this one So these are actually large blind spots the temporal layer which localizes to Tell me a few disorders that you're looking for what's the differential diagnosis for an optic chiasm lesion Mariatinomas apoplexy meningiomas What's the vascular one? Neurism This weird thing Actile is very uh, this is a geniculate lesion So lesion of the lateral geniculate nucleus that the thalamus can give these very strange looking homonymous hemianobias Junctionals ketomas you have a central scatoma on the right left eye Superior temporal so it's catching those medial fibers that are coming. So it's pushing up from the bottom to the chiasm So the lesion is on the left side. It's at the chiasm involving more of the left side more of the More of the optic nerve on the left side more of just the crossing fibers from the right oxidol on the so this is Sparing temporally in the left side So you have a otherwise a left monomous hemianopia. So this localizes to the right occipital the more interior But not totally interior because it's sparing some there How about this make of the clinical scenario for this dial is like like clover leaf like so lazy patient With something going on in the right eye So I made these I was pretty proud of this So relief isn't perfect either, but it's not too bad Any questions that's all I've got for you today


If you really follow the course and you practice it all the way, like we were talking about, security and safety are definite states of mind that go with peace of mind and happiness. But in terms of financial security, in this world, the terms seem to go together and yet when we go much deeper under the surface, I think we could say that that's like an oxymoron, that true security has everything to do with non-judgment, everything to do with being connected to God and everyone and everything, that's perfect security and it really doesn't have anything to do with finances. So in the state of enlightenment, there is not a need for the picture to look a certain way or to have so much money in a bank account or investments. All the things that the ego would say is part of financial security, all those things become actually irrelevant in a state of peace. And so there's no sense of trying to avoid anything or trying to attain anything, there's no sense of trying to get rid of something or to protect something in terms of finances. So I would say in the end, if you follow the course of miracles, you will lose the meaning of financial security and gain the meaning of who you truly are in God's kingdom.


In this video, I'm going to give you three strategies on how to make sure that you get your training in during winter, even when the conditions are horrible. Three strategies to help you through the winter. Hey guys, I just got back from a run in very winterly conditions here in Norway. I'm in my bathroom. I just took off my running clothes, put my normal clothes back on. I'm going to get back to work. But I want to make a video for you guys first, giving you three strategies on how to cope with running in the winter. Because a lot of people struggle with getting their training in during winter, especially in places like Norway, where it's a lot of snow. It's cold. It's dark maybe. It's wind. It might be rain, sleet, snow. You know, conditions can be pretty brutal here. And I don't like it.   But I still get my training in and there's a few things that I've learned about how to make sure that you get that training in. Strategies that are really powerful and I want to share them with you today. Alright, so tip number one relates to the bathroom. The room I'm in right now. Because the bathroom is crucial to a good running routine in winter. Mainly because when you come home from a run, your clothes are going to be sweaty. They're going to be probably wet. You've been out in the snow, in the rain, whatever. You need to put them up to dry. And the best place to do that, of course, is the bathroom where it's warm and usually has good ventilation. And I do recommend having all your running clothes in the bathroom so that it's easily accessible. Because that's the other part of the bathroom tip. When you're heading out into the cold, into the snow, it's mentally difficult and physically difficult.  Maybe it's a little bit chilly.  That's just a horrible start for the whole thing. It makes me, at least, dread it even more. Having to get a little bit cold, taking off my clothes. But if I go into my bathroom where it's very warm and comfortable, tropical conditions, it's fine. I can take off my clothes. I'm comfortable. Maybe I'm listening to music. I'll put on my dry running clothes. I'll get ready. And then I'll head out. And I just find that having, I mean, everyone has a bathroom, obviously. And so it's not like a huge thing. You're already doing it probably. But I just wanted to mention it, you know, hang your running clothes to dry. Do all your changing in the bathroom rather than your bedroom or somewhere else. It's just, I just feel like it's a better way to start your run in somewhere really warm and comfortable. Second tip relates to clothing. Okay. Running clothes. It is crucial that you have quality gear. The equipment is so important during running in winter. I mean, it's always important.  In winter, you've got to get a little bit more technical. And I'm not going to get into sort of the details, the technical details about how to dress for winter running. But what I want to say is that if you're running in, you know, tights that are meant for a little warmer weather and you're a little bit cold, or maybe you have a pair of pants that are not really meant for running, but you use them because it's extra cold these days and you just put on those pants instead because you don't have real running pants. Or, you know, the types of shirts that you're wearing, extra equipment like, you know, neck warmers, hats, beanies, all kinds of stuff like that, headlamp, gloves, all these little things, the socks.  That's, that's horrible.  Okay, so things like that make actually a big difference. So if you're struggling to sort of get your running in in winter and you're dreading the weather, I urge you to invest in some quality clothing. It'll make the whole experience so much better. Okay. All right, third tip, and this is probably the most important one. Okay, it's a mental tip. The first two tips were like practical tips, just have a bathroom, do your changing in the bathroom, dry your clothes in the bathroom, get good quality clothing, practical tips, but here's a mental tip. Okay. For me, training is a priority. And I've already decided before the winter came, before the day comes, before the time for my run comes, I've decided already that I am going to run and the weather is not ever almost something that I consider. Okay. I might look out and think, oh, really, the weather is nice today. I look forward to going out or, oh my God, I'm dreading my run today. It's horrible outside. Sure, I'll have those feelings and those thoughts, but I'm not going to let it influence my decision as to whether I do the run or not. Because as soon as you start allowing those thoughts to creep in, okay, those thoughts like the weather is not really optimal for running it today or it's a bit too cold. I don't think it's healthy to run today or it's very slippery. I might fall. I better wait until tomorrow or as soon as you let those thoughts creep in, your continuity, your consistency in training will fail. You will start to procrastinate and put off, cancel, modify sessions because of the weather, because there's always going to be some challenge in terms of weather, at least here in Norway, in the winter. Okay. So I just don't let it be a factor. Obviously, there are times where it's dangerous.  There are times where you shouldn't run, but that's very, very rare. I don't know of almost ever having skipped a run in the winter due to the weather. I don't think I've ever done it, honestly. So that's my main tip, really, actually. If you're serious about your training, if you're investing time and energy into your training and you want to see results, you have got to do the training. And in order to do the training, you need to have the perseverance in times of difficulties. And the winter can be a difficult time. But if you do, like a lot of people do, and just accept that I won't train as much in winter, I'll start ramping it up again towards the spring. Then you'll go through this cycle where you've lost your fitness through the winter. You're building it up again through the spring and the summer. You're in peak shape racing in autumn. And then you lose your fitness again during the winter. And you go through the same cycle again and again year after year. And you don't really get any better because you're not able to progress and to build and to get that consistency. So you have got to train through winter if you want consistency and progress. Just make the decision already now that you are going to run this winter. And having a plan as well helps you a lot. I'm obviously an online running coach. You can check out my link to my website in the description. I make training plans for my clients. And when they have it there in the calendar, when it's there in the plan, whether I make it for you or you make it yourself, I urge you to have a plan, put it in the calendar and say, you know, on this day, I'm going to run. And maybe it's going to be a great day with fine weather or maybe it's going to be a horrible day with just the absolute worst winter weather ever. Doesn't matter. You've made the decision already. You are going to run. And it just makes it a lot easier. I promise you. That's all. If you have any running tips that you want to share with the community, you could post a comment down below. Something you do maybe to make it easier for you to get through the winter as a runner. Make sure to check out my website, my Instagram link, they're in the description. And stay tuned for more videos, subscribe and like this video, of course. Thanks for watching. Have an awesome day. Bye.


Thank you everyone for joining this session. I know it's the last one. I hope you had a great day here at Cube Day Israel. I know that I enjoyed most of it and talking to most of you. I'm actually really excited to give in the closing session with all of you. Today we'll be speaking about how to simplify your multi-cluster management using a tool called Karmada. A little bit about myself. My name is Eliran Bivas. I'm the architect for the platform group at AppSliar. I work for AppSliar for almost four years now. I have a real passion for technology, so if you look at me in LinkedIn or any other place, you will see that I am a self-proclaimed tech junkie. A little bit about AppSliar. I'll let the numbers speak for themselves, but I'll read out some of them. AppSliar is the market leader for mobile attribution. We operate with 14,000 customers and 65% of the global market share. We have about 1,500 employees that operate across the globe. A little bit about the engineering organization that I'm part of. The engineering group has about roughly 400 engineers divided into squads that operates around 1,200 microservices that handle roughly 3 million events per second. And we operate an infrastructure that is close to 250,000 cloud resources and a dozen of SAS integration and more. The reason it's roughly a number because our infrastructure, as with any other large organization, is growing or shrinking based on the demand and the customer requirements. So a little bit about the agenda that we're going to talk about today. We'll start about the challenges of working with large scale clusters. We'll introduce Karmada and understand what is architecture and a little bit about its API. I'll go over several use cases just to demonstrate the use of Karmada and how it should simplify the use of multi-cluster management and we'll conclude what we discuss in this talk. So let us begin. I'm pretty sure that all of you are familiar with this logo. If not, this is Kubernetes, of course. And I guess for over the years we'll learn to love this tool. Love of hate, it's a matter of perspective. We'll learn to love it because it has a decent scheduling mechanism. It has a simple yet a very robust API to describe our requirements. It has a lot of built-in goodies like service discovery, as node failures and countless integrations that target specifically Kubernetes. It's enough to look at the CNCF landscape just to understand how many different organizations or startups or frameworks target Kubernetes as their infrastructure operating system. But when you reach a certain scale when operating with Kubernetes it forces you to rethink your entire architecture of how to manage that scale. And when it comes to large scale there are basically two options for scaling your large scale clusters. Either you can go with vertical scaling, having a very large disco ball that you keep growing and growing and growing. Or the other way is to use many cluster. Basically try to have as many balls as possible and juggle with them. Each approach has, of course, its advantage and some drawbacks and then try to list some of them in the following slides. First, let's start with the vertical scaling, the very large disco ball. So having a very large disco ball it's basically your single point of failure in the organization. If something happened to that cluster your entire production might be in jeopardy. So having a single point of failure is a big no-no in most of our organizations. Another is a scalability limitation. You can't really have the ball that big. Kubernetes itself has a limitation for its cluster. You can't really reach more than 5,000 nodes. In some cloud provider you can't even reach 3,000 nodes. There is also a limitation for port per node and other limitations that prevent you from growing even larger and larger. Another issue that you will have is resource underutilization. You're going to schedule large workloads operating alongside smaller ones. You get a lot of fragmentation in your bin packing and the cluster is becoming underutilized. Another thing is the complexity of managing a very large cluster. Just think of a simple test if you would like to, let's say, upgrade the cluster API. How long does it take to do a rolling upgrade for a 3,000 node cluster? And it takes quite a while. Next we have a horizontal scaling. So now instead of managing a single cluster, we're going to manage multiple clusters. So just by introducing many clusters we have a complexity of managing of multiple clusters. For example, at App Slayer we manage hundreds of Kubernetes clusters and we have different flavors of clusters. We have clusters targeting Kafka, we have clusters targeting Airflow, Spark, Services, and many, many more each require different type of management and different kind of workloads. So the entire complexity of managing them has become an issue. Resource allocation, this is, again, another difficulty that you need to face with. Basically, when you have so many clusters, which workload you are targeting to which cluster? How do you manage it? So your resource allocation becomes an issue that you need to work with. When you're working with many clusters, your entire network becomes a complexity on its own. How do you do interconnectivity between clusters? Which cluster is allowed to talk to which? And this is a very big challenge if we're facing with service discovery. Because now we need to do a service discovery across multiple clusters. So this is, again, another challenge. And, of course, the last drawback when working with multiple clusters is you have a potential to have an inconsistency of your configuration. Basically, did you install the right controller in all of our clusters? Do we have the same API in all of them? Have we deployed the right deployment to each of our regions? It's a drawback when working with so many clusters. So this is where actually Karmada comes into place. And I'm going to read out loud what basically Karmada is. Karmada, which is a short for Kubernetes Karmada, is a Kubernetes management system that enables you to run cloud-native application across multiple Kubernetes clusters and clouds with no changes to your application. So just by this short statement, we are talking about not just multi-cluster, we are talking about multiple regions, even running on multiple cloud provider. Now, this is a very strong statement, but basically Karmada is aiming to manage your entire global availability of your production. So let's do a short dive into Karmada's architecture. Karmada's control plan is trying to mimic Kubernetes API, so you're going to be familiar with most of the examples I'm going to show you because you're only natively working with Kubernetes. So Karmada's API server mimics the Kubernetes API server. We have a scheduler, but now instead of scheduling two nodes, we are scheduling into clusters. And there are multiple controllers that consist of the entire control plan. One of them, just for an example, is a cluster controller. So if you're familiar with how Kubernetes itself operates, we have a node controller to operate on the node level. Here we are operating on cluster level. There are two options to integrate with the control plan. If you have a cluster that you want Karmada to integrate directly, meaning a push, Karmada will integrate directly with that API server and push the workflows directly to that cluster. Other option is, of course, the pool using an agent. The agent will connect to Karmada's control plan and fetch all the workflows to that designated cluster. A little bit about the primary concept that Karmada is trying to align with. Basically, we're trying to work with these three and I'll later on demonstrate how they are coming into action. First, we have a resource template. Resource templates are the native Kubernetes API you're already familiar with if you know how to work with a deployment, a service, secret, config map, or whatever. It will become available into Karmada's API as a resource template. Any other existing tool that you're currently working with in Kubernetes will become available for you when working with Karmada. There's no need to change anything. Next, we have a propagation policy. The propagation policy is basically the multi-cluster scheduling that allows you to do one-to-many scheduling, having the template propagate to any other cluster that you would like. And last, we have the override policy and the override policy is a cluster-specific configuration that allows you to change the propagation into a much more specific and individual for each cluster or a group of clusters. So let's look at the API flow, for example. The API starts with a resource template. And as I mentioned, everything that needs native to Kubernetes, it's native to in Karmada. So a deployment, config map, and so on. You're submitting into Karmada's API alongside with the propagation and override policy. Everything comes into action. Karmada knows how to push that workflow directly to the designated cluster. Internally, it creates an object called walk. This walk object is responsible to reconcile or synchronize to each of the specific clusters. Now, it doesn't schedule on the cluster itself. The cluster knows how to schedule a deployment or a config map. It knows how to handle a service. It just communicates with the designated cluster through the API and tells it, you need to walk with that object. Internally, everything keeps walking as it should. Now, in most of the diagrams that I show, and later on in some of the other examples that I will show, when you're looking at diagrams, usually in Kubernetes, squares are nodes. Okay? It's pretty simple. We see a lot of nodes, a lot of squares. In Karmada's diagrams, each square is actually a cluster. So it's a much larger scale that you are accustomed to, you see. So let's go over several use cases to demonstrate the multi-cluster API that Karmada provides. I have to say that due to some limitation, specifically space in a slide, I wouldn't be able to show you a complete armada of clusters. I'm going to demonstrate with only two. But just for the sense of it, think of it if we had multiple cluster in the U.S., in Europe, in Asia, mainly in Africa, the entire slide will be a lot of squares. So I'm going to show a very few initial use cases just to demonstrate it. Let's start with the simplest item that Karmada supports. It's, of course, scheduling, how to do a multi-cluster scheduling. And in this example, as I mentioned earlier, we're working with native Kubernetes API. So this is a deployment. I hope you're familiar with it. But it's nothing related to Karmada. It's a simple deployment that we submit to Karmada's API. Nothing special, but nothing happens. When we submit it, this is actually a resource template. Nothing happens on either of the cluster that we are connected to. So if we look at the next step, it's the propagation policy. This is the multi-cluster API that Karmada provides, part of the principles that Karmada is operating with. We are defining a propagation policy, and just for the sake of the example, I use a static propagation. Just for a short demonstration, you usually wouldn't use static configuration. But in this case, we have two cluster, one in the EU, the other in the US. The EU one called EU West One. The EU West One, US East One. Pretty simple. In this static configuration, I'm going to say propagate that deployment that they defined earlier to EU. This is what Karmada will do, schedule it in EU West One. Nothing really happens on EU West. Simple. And again, any square that you see here is a cluster, is not a node specifically. Karmada's API is a cluster. Each one of the EU and the US cluster are fully functional clusters. Next, a more advanced scheduling. Maybe we affinited. Again, this is something that you are familiar with when working with Kubernetes. I'm going to add a label for each of my cluster, one label that's called location based on the continent. In this case, we'll have two. And I'm going to deploy all of my resource templates to the US clusters. So if we'll have multiple clusters, not in this example, we'll deploy all of the resource templates, the resource template to all of our US-based clusters. And a slightly modified scheduling mechanism is an API that is using, again, match expression with labels. Now I'm targeting the US and the EU. Our Asia and Africa cluster will not get any propagation defined. Next, let's see how the override policies come into action. Again, this is a multi-cluster API that Karmada provides. Maybe due to some privacy issues or other business constraints that you have, you need to change the way that services are deployed to your US-based clusters. You're basically using the same label selector as before. And now we're saying, okay, for that cluster, I'm omitting the overriders and rather the possibility there. For example, let's say we're going to use a different environment variable or an image. And now Karmada will schedule the same deployment, but with the overriding scheduling of cluster in the US. A failover. This is another internal mechanism that comes within Karmada's API. I updated the example a little bit. Now the deployment has a replica set to three, meaning that if you schedule it on a regular Kubernetes cluster, we'll get three pots. This is the definition. Again, I'm deploying it to Karmada's API. It's becoming a resource template. And again, I'm going to talk about cluster failover, not node failovers. It's something that Kubernetes is not to do without Karmada, so it doesn't really need to handle it. But this is again a failover mechanism that slightly have a more advanced propagation policy. And again, I'm using static configuration just for the sake of the example. In this case, I'm going to use preferences of a weighted cluster, meaning that I want to change the way that everything is split across my Karmada. I have a scheduling type that it's called divided, meaning that I want to take the entire weight and divide it across my entire clusters. I can also use replicated and other strategies. Again, just for the sake of the example, I've used a weighted and divided because it's much, much easier to understand. And I'm going to use a static that weighs two to the US, one to the EU, meaning that two to the US, one to EU. And again, Karmada doesn't schedule the pods themselves. Karmada is scheduling only the deployments. And those deployments have a slight different propagation based on the propagation policy that we define. And when they reach internally into the designated clusters, two pods appear in the US, one pod appear in the EU. And now catastrophe happened, maybe an entire region has failed or maybe something that we did that causes our cluster in the EU to shut down. In this case, Karmada will identify it and will simply reschedule the deployment, the deployment, not the pod and change the way that the number of replicas will represent the desired state that we wanted, three replicas, now everyone will be in the US. Another example for Karmada's multi-cluster API is service discovery. And now this is something that I personally find very interesting. It's something I am contributing to this project. I wish to keep contributing to enhance its features. We'll start again with a very simple example. We have a deployment and a service. I'm going to omit the propagation policy just for the sake of the example. We propagate it through the Karmada API and have it on the EU West 1 cluster. So now everything runs very simple. We have a deployment and a service that connects into it. So everyone that access the service locally will reach the deployment. Simple, still Kubernetes. When we employ the multi-cluster services API, we say that we want to export that service from the US cluster sorry, from the EU cluster to the US cluster we export from one cluster and import to another. Again, I'm omitting the propagation, everything else. But once we'll have everything running we'll have a service defined in the US that basically once the services will reach it locally will reach EU cluster without having to know that there is no local deployment. Now there are other possibilities under strategies for service discovery you can do failovers, you can do other options how to do service discovery in multiple clusters but this is just the simplest example of having a service that basically does a direct connect to another cluster. But we don't think that I just demonstrated you have to understand that all of the examples that I recently showed you, possesses some risk. And the risk is if you've seen the YAMLs and read it closely you will probably see that the API version was v1 alpha 1 meaning that while some company do use Karmada in production you have to understand that this is a CNCF sandbox project it means that the API is not finalized or should be considered stable so if you're planning on using it you should definitely consider the risk of using a sandbox project and as a sandbox project or any other open source project it requires a lot of contribution from its audience and users first you should access the website in karmadas.io there's a lot of documentation that the team has provided a very well documented code and a very well documented feature set you can also open a lot of issues and contribute of course code to their GitHub repository it's highly appreciated and of course join the discussion, there are a lot of discussions over the CNCF Slack over at Karmadas and any contribution will be much helpful so let us conclude a little bit about what we have discussed in the past 20- so minutes first we discussed about Kubernetes and how it used to ease our work our operational work we mentioned that once we reach a certain amount of scale we need to rethink our operating strategy we talked about vertical scaling versus horizontal scaling having the discoball versus number of balls and what are the downsides for each of the approaches and last we talked about karmada, its architecture and very very initial use cases just to get a glimpse of its multi cluster API thank you very much thank you very much Aliran and we have a few minutes for questions any questions from the audience okay I see a few hands here let's start here so my question is regarding your experience in scaling at Apslyre before you when you made the decision to scale horizontally did you, what was the limit that you discovered practically on vertical scaling sorry on horizontal scaling of a single cluster before you decided that you had to go split workers to multiple clusters in Apslyre we decided that we immediately going to go with horizontal scaling because of the amount of different workflow that we have since we have workflows that targeting Kafka, air flow services, they are all different in shapes and sizes so we immediately started with horizontal scaling next question here we go can you please say how Kafka is different from OCM open cluster management and why would they choose one of the other I guess this is a topic for another for another conversation so maybe we could talk yeah, let's stick to this because it's a big subject and I can actually feeling another 30 minutes for it more questions, here we go when you deploy an application across multiple clusters and let's say it deployed everything went successfully who's responsible for the deployment if it, let's say changed somehow someone changed it so it looks on it and checks if it changed and reverted to the initial state and because let's say if I use rgo cd to manage my applications and I want to deploy all the application across multiple clusters I can use both but since rgo cd is the manager of the application it might change something and if this one will change it back it will go back and forth I think you can answer your question because the key here is githubs you basically need to have the entire api propagate with githubs so if you are managing today your entire clusters with rgo cd or flux to manage your clusters you basically have the same notions of githubs everything the source of truth for you is still your github so if something changes across the cluster it will propagate again and reconcile to your source of truth more questions okay we have here the corner here we go okay a couple of questions about commander first can you also handle things like changing a community's version or it just handles the deployment and following up with this question does commander have githubs of its own because if I understand correctly instead of writing infrastructure as code that goes directly to the community's cluster you have to write infrastructure as code that goes to commander to handle all of it so it should have the same tools of managing codes and configuration on its own so I'll start with the second one actually but no it doesn't have its own githubs it relies on reconciling itself this is why it has come out as api and you're supposed to bring in all your yaml's and configuration from another source in this case maybe rgo or maybe flux to bringing your configuration answer the second part of your question okay and for the first part I need you to ask it again sorry so you mentioned a few drawbacks of using multiple clusters like inconsistencies of configuration between clusters how does if it does commander resolve those issues it actually doesn't this is part of being a sandbox it doesn't really target it yet any other questions just a second here we go in the example you gave with deployment of multiple replicas that got divided between two clusters how is pod disruption budget handled in that example you basically if you know how to work with pod distribution budget in a single cluster it's the same with karmada's api it's submitted and propagated to the clusters and it will keep working as the same but if my deployment is let's say I want to have a max of one unavailable but I have one cluster with one deployment with one replica and another cluster with two replicas what would be the pdb that gets set on each of those so I showed a static configuration so usually wouldn't use that a specific number of pods this contradicts working with auto scaling and contradicts budgeting and so on so if you're working with budgeting there is another api for that I didn't show it because it's a much more advanced one but karmada knows how to handle it there's a different one there's a question on this side of the house here we go first question CRDs are they supported yep okay that's good and the second thing some infrastructure providers like Pulumi and Terraform rely on the status of the deployments so in this case because when deployment is actually multiple deployments how does the status field change I'm sure it's not the same as one single deployment so karmada's api is the source of truth for you usually if you deploy with Terraform, Terraform looks as a single cluster right but now we are working on multiple cluster so karmada is your entry point so Terraform operates on the karmada api level if you apply deployment to a cluster in Terraform it waits on the deployment status to be complete so in this case what's the status because there's 10 clusters and I'm heard it's a different syntax or do you even have a status yeah it's the native if you do kubectl describe the deployment you will get the status fit as if it was running on the karmada api oh also like the complete is on every single cluster combined thank you very much and you run great round of applause great talk